apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:46:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-27-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-27.us-west-1.compute.internal
      uid: 64939808-0156-4b4f-a4c4-89e37a9bb48f
    resourceVersion: "100215"
    uid: 14f72f89-4d04-4fce-b16d-68278f0c8fde
  spec:
    sourcePod: network-check-source-6f78d59f99-69s2p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:53:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.755621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:49:04Z"
    - latency: 939.763µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:48:04Z"
    - latency: 871.406µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:47:04Z"
    - latency: 1.00622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 1.91285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 1.038501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 1.389523ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 1.56363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:42:04Z"
    - latency: 1.021937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:41:04Z"
    - latency: 868.114µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:46:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-27-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-27.us-west-1.compute.internal
      uid: 64939808-0156-4b4f-a4c4-89e37a9bb48f
    resourceVersion: "97845"
    uid: 703d32d1-c243-40b2-a062-0a3bfc4d5ab5
  spec:
    sourcePod: network-check-source-6f78d59f99-69s2p
    targetEndpoint: a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:52:04Z"
      message: 'load-balancer-api-external: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.369181ms
      message: 'load-balancer-api-external: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 7.697203ms
      message: 'load-balancer-api-external: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 54.893118ms
      message: 'load-balancer-api-external: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 6.8479ms
      message: 'load-balancer-api-external: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 54.806178ms
      message: 'load-balancer-api-external: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 6.47235ms
      message: 'load-balancer-api-external: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 55.523619ms
      message: 'load-balancer-api-external: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 5.987189ms
      message: 'load-balancer-api-external: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 56.149184ms
      message: 'load-balancer-api-external: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:42:04Z"
    - latency: 8.046375ms
      message: 'load-balancer-api-external: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:46:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-27-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-27.us-west-1.compute.internal
      uid: 64939808-0156-4b4f-a4c4-89e37a9bb48f
    resourceVersion: "97846"
    uid: 42efb080-16f1-423a-84b7-e77abc515c45
  spec:
    sourcePod: network-check-source-6f78d59f99-69s2p
    targetEndpoint: a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:52:04Z"
      message: 'load-balancer-api-internal: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.319392ms
      message: 'load-balancer-api-internal: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 7.830664ms
      message: 'load-balancer-api-internal: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 54.850324ms
      message: 'load-balancer-api-internal: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 6.961386ms
      message: 'load-balancer-api-internal: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 55.26092ms
      message: 'load-balancer-api-internal: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 6.54252ms
      message: 'load-balancer-api-internal: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 55.536295ms
      message: 'load-balancer-api-internal: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 6.068379ms
      message: 'load-balancer-api-internal: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 56.157577ms
      message: 'load-balancer-api-internal: tcp connection to a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:42:04Z"
    - latency: 7.705731ms
      message: 'load-balancer-api-internal: resolved host name a8a25ac9f0dfc4e67bf96bf3051bc6f6-5b74f0dd39b75e91.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:42:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:46:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-27-to-network-check-target-ip-10-0-130-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-27.us-west-1.compute.internal
      uid: 64939808-0156-4b4f-a4c4-89e37a9bb48f
    resourceVersion: "100214"
    uid: ef476ea0-dfd8-405b-b1d8-34c7ac976116
  spec:
    sourcePod: network-check-source-6f78d59f99-69s2p
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:53:04Z"
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.532099ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:49:04Z"
    - latency: 2.182655ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:48:04Z"
    - latency: 2.308482ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:47:04Z"
    - latency: 2.412746ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 2.189227ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 1.97399ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 2.287114ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 2.820069ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:42:04Z"
    - latency: 1.947118ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:41:04Z"
    - latency: 2.190129ms
      message: 'network-check-target-ip-10-0-130-41: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:46:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-27-to-network-check-target-ip-10-0-133-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-27.us-west-1.compute.internal
      uid: 64939808-0156-4b4f-a4c4-89e37a9bb48f
    resourceVersion: "100212"
    uid: 56e7984d-d3f0-4075-8f88-3f9970872d2a
  spec:
    sourcePod: network-check-source-6f78d59f99-69s2p
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:53:04Z"
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.208µs
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:49:04Z"
    - latency: 1.099584ms
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:48:04Z"
    - latency: 1.166783ms
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:47:04Z"
    - latency: 900.187µs
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 1.165369ms
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 1.419713ms
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 899.727µs
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 2.131919ms
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:42:04Z"
    - latency: 958.008µs
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:41:04Z"
    - latency: 936.77µs
      message: 'network-check-target-ip-10-0-133-27: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:46:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-27-to-network-check-target-ip-10-0-142-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-27.us-west-1.compute.internal
      uid: 64939808-0156-4b4f-a4c4-89e37a9bb48f
    resourceVersion: "100213"
    uid: 5685e80e-ca89-49a1-b0a7-8f602da09bd6
  spec:
    sourcePod: network-check-source-6f78d59f99-69s2p
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:53:04Z"
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.67676ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:49:04Z"
    - latency: 1.723127ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:48:04Z"
    - latency: 1.83606ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:47:04Z"
    - latency: 1.93412ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 1.954893ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 1.551503ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 1.941036ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 2.667192ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:42:04Z"
    - latency: 1.692959ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:41:04Z"
    - latency: 1.885532ms
      message: 'network-check-target-ip-10-0-142-240: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:46:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-27-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-27.us-west-1.compute.internal
      uid: 64939808-0156-4b4f-a4c4-89e37a9bb48f
    resourceVersion: "97842"
    uid: de0f692b-5f37-4344-bbae-aabcbe808441
  spec:
    sourcePod: network-check-source-6f78d59f99-69s2p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:52:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.357µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 2.283719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:46:04Z"
    - latency: 1.097978ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 2.08755ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:45:04Z"
    - latency: 924.586µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 1.890144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:44:04Z"
    - latency: 978.249µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 1.810313ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:43:04Z"
    - latency: 902.103µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:42:04Z"
    - latency: 2.823393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:42:04Z"
kind: List
metadata:
  resourceVersion: ""