apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:33:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 5de6bb1a-2933-4f56-8790-11784b465c33
    resourceVersion: "19491"
    uid: df726f31-15fe-4273-95e8-7a0512637a81
  spec:
    sourcePod: network-check-source-6f8b768455-ckc9d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:40:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.74369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 1.027126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:53:28Z"
    - latency: 1.052431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:52:28Z"
    - latency: 1.241438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:51:28Z"
    - latency: 1.00044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:50:28Z"
    - latency: 932.92µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:49:28Z"
    - latency: 937.938µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:48:28Z"
    - latency: 931.659µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:47:28Z"
    - latency: 950.196µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:46:28Z"
    - latency: 1.079804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:33:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 5de6bb1a-2933-4f56-8790-11784b465c33
    resourceVersion: "20749"
    uid: 9e2d184b-c86b-44af-afa6-b55387ed5bc5
  spec:
    sourcePod: network-check-source-6f8b768455-ckc9d
    targetEndpoint: a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:39:28Z"
      message: 'load-balancer-api-external: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.05922ms
      message: 'load-balancer-api-external: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:57:28Z"
    - latency: 6.513416ms
      message: 'load-balancer-api-external: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:57:28Z"
    - latency: 4.03667ms
      message: 'load-balancer-api-external: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:56:28Z"
    - latency: 6.86141ms
      message: 'load-balancer-api-external: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:56:28Z"
    - latency: 5.311459ms
      message: 'load-balancer-api-external: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:55:28Z"
    - latency: 6.30016ms
      message: 'load-balancer-api-external: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:55:28Z"
    - latency: 7.592876ms
      message: 'load-balancer-api-external: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 7.733072ms
      message: 'load-balancer-api-external: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 4.434087ms
      message: 'load-balancer-api-external: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:53:28Z"
    - latency: 6.911276ms
      message: 'load-balancer-api-external: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:53:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:33:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 5de6bb1a-2933-4f56-8790-11784b465c33
    resourceVersion: "20750"
    uid: bbd63b09-b8c7-4bd6-84fd-43e6a2c3833e
  spec:
    sourcePod: network-check-source-6f8b768455-ckc9d
    targetEndpoint: a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:39:28Z"
      message: 'load-balancer-api-internal: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.061061ms
      message: 'load-balancer-api-internal: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:57:28Z"
    - latency: 6.493258ms
      message: 'load-balancer-api-internal: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:57:28Z"
    - latency: 4.022471ms
      message: 'load-balancer-api-internal: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:56:28Z"
    - latency: 6.885059ms
      message: 'load-balancer-api-internal: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:56:28Z"
    - latency: 5.297238ms
      message: 'load-balancer-api-internal: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:55:28Z"
    - latency: 6.340187ms
      message: 'load-balancer-api-internal: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:55:28Z"
    - latency: 6.581049ms
      message: 'load-balancer-api-internal: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 7.796007ms
      message: 'load-balancer-api-internal: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 4.483094ms
      message: 'load-balancer-api-internal: tcp connection to a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:53:28Z"
    - latency: 6.940299ms
      message: 'load-balancer-api-internal: resolved host name a6a380c63c56349d898a11f2822e092a-53e3c9115cdcd248.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:53:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:33:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-ip-10-0-128-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 5de6bb1a-2933-4f56-8790-11784b465c33
    resourceVersion: "19487"
    uid: e36783d8-87e7-407b-828e-9d97a899adc1
  spec:
    sourcePod: network-check-source-6f8b768455-ckc9d
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:40:28Z"
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.943µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 1.361032ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:53:28Z"
    - latency: 849.324µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:52:28Z"
    - latency: 1.150339ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:51:28Z"
    - latency: 1.330562ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:50:28Z"
    - latency: 935.236µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:49:28Z"
    - latency: 897.109µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:48:28Z"
    - latency: 887.882µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:47:28Z"
    - latency: 1.573545ms
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:46:28Z"
    - latency: 898.656µs
      message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:33:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-ip-10-0-138-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 5de6bb1a-2933-4f56-8790-11784b465c33
    resourceVersion: "19490"
    uid: da58291b-168b-435c-b3cf-7a7b2daa8410
  spec:
    sourcePod: network-check-source-6f8b768455-ckc9d
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:40:28Z"
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.966599ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 2.63902ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:53:28Z"
    - latency: 2.205811ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:52:28Z"
    - latency: 2.506203ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:51:28Z"
    - latency: 4.786157ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:50:28Z"
    - latency: 2.03597ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:49:28Z"
    - latency: 2.053999ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:48:28Z"
    - latency: 2.29701ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:47:28Z"
    - latency: 2.092439ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:46:28Z"
    - latency: 2.570354ms
      message: 'network-check-target-ip-10-0-138-157: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:33:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-ip-10-0-142-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 5de6bb1a-2933-4f56-8790-11784b465c33
    resourceVersion: "19488"
    uid: d5961737-bc8b-49a2-8801-9fc2d8a59a1c
  spec:
    sourcePod: network-check-source-6f8b768455-ckc9d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:40:28Z"
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.236375ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 2.724171ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:53:28Z"
    - latency: 2.258528ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:52:28Z"
    - latency: 1.994064ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:51:28Z"
    - latency: 5.392047ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:50:28Z"
    - latency: 2.138837ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:49:28Z"
    - latency: 2.082264ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:48:28Z"
    - latency: 2.524796ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:47:28Z"
    - latency: 2.582779ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:46:28Z"
    - latency: 2.180108ms
      message: 'network-check-target-ip-10-0-142-17: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:45:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:33:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-196-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-196.ec2.internal
      uid: 5de6bb1a-2933-4f56-8790-11784b465c33
    resourceVersion: "20748"
    uid: cd515c8f-6d79-4978-819b-d7596231649a
  spec:
    sourcePod: network-check-source-6f8b768455-ckc9d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:39:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.130007ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:57:28Z"
    - latency: 1.708161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:57:28Z"
    - latency: 725.655µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:56:28Z"
    - latency: 2.138087ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:56:28Z"
    - latency: 1.157018ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:55:28Z"
    - latency: 1.647264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:55:28Z"
    - latency: 910.812µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 1.727009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:54:28Z"
    - latency: 868.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T11:53:28Z"
    - latency: 2.16272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T11:53:28Z"
kind: List
metadata:
  resourceVersion: ""