apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:21:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-147-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-147.ec2.internal
      uid: 1774d3b5-a724-4417-b460-a4d67b8afde2
    resourceVersion: "17787"
    uid: 9221c857-6ed4-400c-a710-7abfc2d7b41c
  spec:
    sourcePod: network-check-source-7cbc45fddc-pjjd4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:28:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.101606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:59Z"
    - latency: 1.026578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:59Z"
    - latency: 1.326535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 979.737µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 1.038662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 1.025528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 1.097175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:59Z"
    - latency: 1.278247ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:59Z"
    - latency: 1.121042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:59Z"
    - latency: 1.146332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:21:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-147-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-147.ec2.internal
      uid: 1774d3b5-a724-4417-b460-a4d67b8afde2
    resourceVersion: "16935"
    uid: b38f5fd6-fd24-42a9-a425-4b0c930eaddc
  spec:
    sourcePod: network-check-source-7cbc45fddc-pjjd4
    targetEndpoint: a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:27:59Z"
      message: 'load-balancer-api-external: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.842473ms
      message: 'load-balancer-api-external: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 8.172836ms
      message: 'load-balancer-api-external: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 5.949407ms
      message: 'load-balancer-api-external: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 8.609997ms
      message: 'load-balancer-api-external: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 5.847524ms
      message: 'load-balancer-api-external: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 6.968792ms
      message: 'load-balancer-api-external: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 6.531761ms
      message: 'load-balancer-api-external: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 8.725688ms
      message: 'load-balancer-api-external: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 4.883302ms
      message: 'load-balancer-api-external: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:59Z"
    - latency: 6.67158ms
      message: 'load-balancer-api-external: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:29:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:21:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-147-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-147.ec2.internal
      uid: 1774d3b5-a724-4417-b460-a4d67b8afde2
    resourceVersion: "16934"
    uid: 455200b1-3291-4498-a5f8-ba6be358bcbd
  spec:
    sourcePod: network-check-source-7cbc45fddc-pjjd4
    targetEndpoint: a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:27:59Z"
      message: 'load-balancer-api-internal: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.796602ms
      message: 'load-balancer-api-internal: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 8.216331ms
      message: 'load-balancer-api-internal: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 6.577484ms
      message: 'load-balancer-api-internal: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 8.676957ms
      message: 'load-balancer-api-internal: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 5.855473ms
      message: 'load-balancer-api-internal: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 6.882533ms
      message: 'load-balancer-api-internal: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 6.559481ms
      message: 'load-balancer-api-internal: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 8.790906ms
      message: 'load-balancer-api-internal: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 5.859209ms
      message: 'load-balancer-api-internal: tcp connection to a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:59Z"
    - latency: 6.636839ms
      message: 'load-balancer-api-internal: resolved host name a351e116f591c40e286f66894dddfda8-fad4233e09ceb6df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:29:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:21:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-147-to-network-check-target-ip-10-0-135-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-147.ec2.internal
      uid: 1774d3b5-a724-4417-b460-a4d67b8afde2
    resourceVersion: "17785"
    uid: 64fc80b3-d8cb-4873-b442-bf73851a0512
  spec:
    sourcePod: network-check-source-7cbc45fddc-pjjd4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:28:59Z"
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.147176ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:59Z"
    - latency: 1.939222ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:59Z"
    - latency: 2.27481ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 2.232788ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 2.382648ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 2.237187ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 2.979125ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:59Z"
    - latency: 2.114107ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:59Z"
    - latency: 2.345105ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:59Z"
    - latency: 2.244661ms
      message: 'network-check-target-ip-10-0-135-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:21:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-147-to-network-check-target-ip-10-0-140-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-147.ec2.internal
      uid: 1774d3b5-a724-4417-b460-a4d67b8afde2
    resourceVersion: "17784"
    uid: 9ff72005-a21b-4dd0-aa74-92210eba674a
  spec:
    sourcePod: network-check-source-7cbc45fddc-pjjd4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:28:59Z"
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.953µs
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:59Z"
    - latency: 983.541µs
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:59Z"
    - latency: 967.966µs
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 1.398818ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 1.069454ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 832.373µs
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 902.674µs
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:59Z"
    - latency: 1.362724ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:59Z"
    - latency: 1.0124ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:59Z"
    - latency: 1.336881ms
      message: 'network-check-target-ip-10-0-140-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:21:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-147-to-network-check-target-ip-10-0-140-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-147.ec2.internal
      uid: 1774d3b5-a724-4417-b460-a4d67b8afde2
    resourceVersion: "17786"
    uid: 5c049b87-9594-4318-88be-69898e572056
  spec:
    sourcePod: network-check-source-7cbc45fddc-pjjd4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:28:59Z"
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.67163ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:35:59Z"
    - latency: 2.359674ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:34:59Z"
    - latency: 2.29486ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 2.151134ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 2.480056ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 2.388601ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 2.192083ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:59Z"
    - latency: 2.305618ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:28:59Z"
    - latency: 2.098857ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:27:59Z"
    - latency: 2.192545ms
      message: 'network-check-target-ip-10-0-140-185: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:26:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:21:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-147-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-147.ec2.internal
      uid: 1774d3b5-a724-4417-b460-a4d67b8afde2
    resourceVersion: "16933"
    uid: 6d16e025-f757-405d-b757-ce5e89a51b22
  spec:
    sourcePod: network-check-source-7cbc45fddc-pjjd4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:27:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.761µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 1.641663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:33:59Z"
    - latency: 819.726µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 1.946634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:32:59Z"
    - latency: 796.709µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 1.778869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:31:59Z"
    - latency: 758.835µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 1.807949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:30:59Z"
    - latency: 887.072µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T13:29:59Z"
    - latency: 1.699001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T13:29:59Z"
kind: List
metadata:
  resourceVersion: ""