apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:22:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: cc05f003-2072-4a35-a90f-305c6b6ad9e4
    resourceVersion: "53743"
    uid: a99588c3-7161-44dc-86f9-d76d8649b422
  spec:
    sourcePod: network-check-source-685456655f-dj7p4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:29:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.291646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 999.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 1.007504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:48:46Z"
    - latency: 1.118404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:47:46Z"
    - latency: 1.072795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:46:46Z"
    - latency: 1.074277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:46Z"
    - latency: 1.357691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:46Z"
    - latency: 803.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:46Z"
    - latency: 1.610829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:46Z"
    - latency: 2.719056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:22:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: cc05f003-2072-4a35-a90f-305c6b6ad9e4
    resourceVersion: "55429"
    uid: 286dd4de-543f-4c68-809c-353b49e69ff2
  spec:
    sourcePod: network-check-source-685456655f-dj7p4
    targetEndpoint: a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:28:46Z"
      message: 'load-balancer-api-external: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.842139ms
      message: 'load-balancer-api-external: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:52:46Z"
    - latency: 7.097447ms
      message: 'load-balancer-api-external: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:52:46Z"
    - latency: 5.423145ms
      message: 'load-balancer-api-external: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:51:46Z"
    - latency: 8.135926ms
      message: 'load-balancer-api-external: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:51:46Z"
    - latency: 5.509641ms
      message: 'load-balancer-api-external: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 9.937221ms
      message: 'load-balancer-api-external: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 5.529559ms
      message: 'load-balancer-api-external: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 8.336144ms
      message: 'load-balancer-api-external: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 4.073925ms
      message: 'load-balancer-api-external: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:48:46Z"
    - latency: 9.719168ms
      message: 'load-balancer-api-external: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:22:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: cc05f003-2072-4a35-a90f-305c6b6ad9e4
    resourceVersion: "55430"
    uid: 81b32a34-e8b5-4756-a746-6cd0e5b54aa4
  spec:
    sourcePod: network-check-source-685456655f-dj7p4
    targetEndpoint: a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:28:46Z"
      message: 'load-balancer-api-internal: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.870897ms
      message: 'load-balancer-api-internal: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:52:46Z"
    - latency: 7.082176ms
      message: 'load-balancer-api-internal: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:52:46Z"
    - latency: 5.50538ms
      message: 'load-balancer-api-internal: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:51:46Z"
    - latency: 8.103518ms
      message: 'load-balancer-api-internal: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:51:46Z"
    - latency: 4.797097ms
      message: 'load-balancer-api-internal: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 9.9208ms
      message: 'load-balancer-api-internal: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 18.492269ms
      message: 'load-balancer-api-internal: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 8.228722ms
      message: 'load-balancer-api-internal: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 4.087726ms
      message: 'load-balancer-api-internal: tcp connection to a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:48:46Z"
    - latency: 9.691467ms
      message: 'load-balancer-api-internal: resolved host name a9a2b8303bd46431fb94653a1824789e-b891a90ae450bdef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:48:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:22:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-128-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: cc05f003-2072-4a35-a90f-305c6b6ad9e4
    resourceVersion: "53740"
    uid: 3903d5b9-1f2c-45fa-b545-0912d27ed109
  spec:
    sourcePod: network-check-source-685456655f-dj7p4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:29:46Z"
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.262525ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 1.161066ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 996.235µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:48:46Z"
    - latency: 1.145489ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:47:46Z"
    - latency: 1.549638ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:46:46Z"
    - latency: 1.146883ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:46Z"
    - latency: 1.379159ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:46Z"
    - latency: 1.897835ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:46Z"
    - latency: 1.082288ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:46Z"
    - latency: 1.723744ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:22:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-135-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: cc05f003-2072-4a35-a90f-305c6b6ad9e4
    resourceVersion: "53742"
    uid: 702d9b30-ab39-4346-a2a6-767e14b97e88
  spec:
    sourcePod: network-check-source-685456655f-dj7p4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:29:46Z"
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.448764ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 2.452603ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 2.108213ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:48:46Z"
    - latency: 2.392028ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:47:46Z"
    - latency: 2.55964ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:46:46Z"
    - latency: 2.834837ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:46Z"
    - latency: 3.085514ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:46Z"
    - latency: 2.746776ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:46Z"
    - latency: 2.559665ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:46Z"
    - latency: 3.130563ms
      message: 'network-check-target-ip-10-0-135-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:22:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-138-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: cc05f003-2072-4a35-a90f-305c6b6ad9e4
    resourceVersion: "53741"
    uid: f130dfd7-5b5b-405e-9cb1-0fac7a94fde7
  spec:
    sourcePod: network-check-source-685456655f-dj7p4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:29:46Z"
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.515012ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 2.619407ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 2.494835ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:48:46Z"
    - latency: 2.426784ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:47:46Z"
    - latency: 2.841429ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:46:46Z"
    - latency: 2.491344ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:45:46Z"
    - latency: 2.826157ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:44:46Z"
    - latency: 3.198361ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:43:46Z"
    - latency: 2.724408ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:42:46Z"
    - latency: 2.139794ms
      message: 'network-check-target-ip-10-0-138-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:41:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:22:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: cc05f003-2072-4a35-a90f-305c6b6ad9e4
    resourceVersion: "55428"
    uid: e552be0d-e8c8-4682-977f-ca16713a6ef1
  spec:
    sourcePod: network-check-source-685456655f-dj7p4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:28:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.144275ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:52:46Z"
    - latency: 1.939454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:52:46Z"
    - latency: 1.300495ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:51:46Z"
    - latency: 2.023235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:51:46Z"
    - latency: 1.010969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 2.588592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:50:46Z"
    - latency: 915.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 1.799957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:49:46Z"
    - latency: 1.163608ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:48:46Z"
    - latency: 2.301212ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:48:46Z"
kind: List
metadata:
  resourceVersion: ""