apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 0b7d35fa-9b7f-4b2a-8a7d-c68786aedae1
    resourceVersion: "48389"
    uid: 41ad1e68-fca1-4b9d-b07e-1012c2eabebe
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nrqtf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:53:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.715117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 962.742µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 991.085µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:12:45Z"
    - latency: 1.30484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:11:45Z"
    - latency: 1.173256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:10:45Z"
    - latency: 1.111348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:09:45Z"
    - latency: 1.150331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:08:45Z"
    - latency: 969.045µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:45Z"
    - latency: 1.242569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:45Z"
    - latency: 1.063698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 0b7d35fa-9b7f-4b2a-8a7d-c68786aedae1
    resourceVersion: "50847"
    uid: 85679562-ac77-4c59-864f-f26ab7e03d63
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nrqtf
    targetEndpoint: a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:52:45Z"
      message: 'load-balancer-api-external: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.103407ms
      message: 'load-balancer-api-external: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:16:45Z"
    - latency: 6.455918ms
      message: 'load-balancer-api-external: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:16:45Z"
    - latency: 4.202545ms
      message: 'load-balancer-api-external: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:15:45Z"
    - latency: 7.017438ms
      message: 'load-balancer-api-external: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:15:45Z"
    - latency: 3.657782ms
      message: 'load-balancer-api-external: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 6.929289ms
      message: 'load-balancer-api-external: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 3.493879ms
      message: 'load-balancer-api-external: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 8.608906ms
      message: 'load-balancer-api-external: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 4.854822ms
      message: 'load-balancer-api-external: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:12:45Z"
    - latency: 8.617845ms
      message: 'load-balancer-api-external: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:12:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 0b7d35fa-9b7f-4b2a-8a7d-c68786aedae1
    resourceVersion: "50846"
    uid: 7d698dd9-62ae-4233-8af7-a75d30b1af36
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nrqtf
    targetEndpoint: a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:52:45Z"
      message: 'load-balancer-api-internal: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.092534ms
      message: 'load-balancer-api-internal: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:16:45Z"
    - latency: 6.407416ms
      message: 'load-balancer-api-internal: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:16:45Z"
    - latency: 4.375483ms
      message: 'load-balancer-api-internal: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:15:45Z"
    - latency: 6.964139ms
      message: 'load-balancer-api-internal: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:15:45Z"
    - latency: 4.257337ms
      message: 'load-balancer-api-internal: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 6.994704ms
      message: 'load-balancer-api-internal: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 4.620801ms
      message: 'load-balancer-api-internal: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 8.558709ms
      message: 'load-balancer-api-internal: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 4.840806ms
      message: 'load-balancer-api-internal: tcp connection to a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:12:45Z"
    - latency: 8.485146ms
      message: 'load-balancer-api-internal: resolved host name a42abf17aaf744dbd91899cfe365c3a5-76d8a1f53574ef15.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:12:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-ip-10-0-130-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 0b7d35fa-9b7f-4b2a-8a7d-c68786aedae1
    resourceVersion: "48388"
    uid: bfca249c-b740-43f9-81d9-11d256cc3d1a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nrqtf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:53:45Z"
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.401415ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 1.876704ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 2.216975ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:12:45Z"
    - latency: 2.187767ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:11:45Z"
    - latency: 2.060052ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:10:45Z"
    - latency: 1.838478ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:09:45Z"
    - latency: 2.198083ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:08:45Z"
    - latency: 2.277987ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:45Z"
    - latency: 2.177617ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:45Z"
    - latency: 2.423658ms
      message: 'network-check-target-ip-10-0-130-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-ip-10-0-136-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 0b7d35fa-9b7f-4b2a-8a7d-c68786aedae1
    resourceVersion: "48386"
    uid: 3cce87a7-1ab1-4539-a419-12a81a47c797
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nrqtf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:53:45Z"
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.187µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 880.679µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 970.937µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:12:45Z"
    - latency: 977.787µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:11:45Z"
    - latency: 873.233µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:10:45Z"
    - latency: 841.252µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:09:45Z"
    - latency: 944.577µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:08:45Z"
    - latency: 1.008921ms
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:45Z"
    - latency: 940.519µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:45Z"
    - latency: 987.125µs
      message: 'network-check-target-ip-10-0-136-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-ip-10-0-142-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 0b7d35fa-9b7f-4b2a-8a7d-c68786aedae1
    resourceVersion: "48387"
    uid: 61894e56-7d6a-4d65-b3cf-38b2b408f1ee
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nrqtf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:53:45Z"
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.108474ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 1.788481ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 2.008055ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:12:45Z"
    - latency: 2.164187ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:11:45Z"
    - latency: 2.282797ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:10:45Z"
    - latency: 2.191106ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:09:45Z"
    - latency: 2.280953ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:08:45Z"
    - latency: 1.942842ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:07:45Z"
    - latency: 1.940168ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:06:45Z"
    - latency: 2.009089ms
      message: 'network-check-target-ip-10-0-142-221: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:05:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T00:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-82.ec2.internal
      uid: 0b7d35fa-9b7f-4b2a-8a7d-c68786aedae1
    resourceVersion: "50844"
    uid: 5f8980bc-0136-4832-b7cf-f73d9bd4d8f6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-nrqtf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T00:52:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.333157ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:16:45Z"
    - latency: 1.676111ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:16:45Z"
    - latency: 929.322µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:15:45Z"
    - latency: 1.800879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:15:45Z"
    - latency: 762.946µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 1.97515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:14:45Z"
    - latency: 860.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 1.61495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:13:45Z"
    - latency: 910.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T01:12:45Z"
    - latency: 1.686938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T01:12:45Z"
kind: List
metadata:
  resourceVersion: ""