apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:31:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-113-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-113.ec2.internal
      uid: 911c686d-2d7f-4485-83d2-248b43aef371
    resourceVersion: "16705"
    uid: 975d7bad-a9be-4aaf-b2f2-f2ed6d1ae93a
  spec:
    sourcePod: network-check-source-dbd9cf844-rdvxr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:38:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 793.759µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:45:31Z"
    - latency: 1.009708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:44:31Z"
    - latency: 1.278591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 1.094417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 807.029µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 813.348µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 1.094692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:39:31Z"
    - latency: 1.000364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:38:31Z"
    - latency: 1.44319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:37:31Z"
    - latency: 1.176126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:31:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-113-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-113.ec2.internal
      uid: 911c686d-2d7f-4485-83d2-248b43aef371
    resourceVersion: "15950"
    uid: 6b5ee912-e671-433f-9291-788ebfb650b5
  spec:
    sourcePod: network-check-source-dbd9cf844-rdvxr
    targetEndpoint: ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:37:31Z"
      message: 'load-balancer-api-external: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.732395ms
      message: 'load-balancer-api-external: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 8.0464ms
      message: 'load-balancer-api-external: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 5.409736ms
      message: 'load-balancer-api-external: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 8.629868ms
      message: 'load-balancer-api-external: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 4.814669ms
      message: 'load-balancer-api-external: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 9.985467ms
      message: 'load-balancer-api-external: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 4.748883ms
      message: 'load-balancer-api-external: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 8.903885ms
      message: 'load-balancer-api-external: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 5.033083ms
      message: 'load-balancer-api-external: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:39:31Z"
    - latency: 8.528081ms
      message: 'load-balancer-api-external: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:39:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:31:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-113-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-113.ec2.internal
      uid: 911c686d-2d7f-4485-83d2-248b43aef371
    resourceVersion: "15949"
    uid: 0572396e-6891-4644-894e-55bbed5d7791
  spec:
    sourcePod: network-check-source-dbd9cf844-rdvxr
    targetEndpoint: ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:37:31Z"
      message: 'load-balancer-api-internal: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.381326ms
      message: 'load-balancer-api-internal: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 8.115844ms
      message: 'load-balancer-api-internal: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 5.403413ms
      message: 'load-balancer-api-internal: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 8.678618ms
      message: 'load-balancer-api-internal: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 4.848903ms
      message: 'load-balancer-api-internal: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 9.978727ms
      message: 'load-balancer-api-internal: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 4.813638ms
      message: 'load-balancer-api-internal: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 8.892786ms
      message: 'load-balancer-api-internal: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 4.995351ms
      message: 'load-balancer-api-internal: tcp connection to ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:39:31Z"
    - latency: 8.600986ms
      message: 'load-balancer-api-internal: resolved host name ab70719fb6b134202884332dce4d1d46-031a2dc6abef1735.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:39:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:31:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-113-to-network-check-target-ip-10-0-134-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-113.ec2.internal
      uid: 911c686d-2d7f-4485-83d2-248b43aef371
    resourceVersion: "16704"
    uid: c79dca1e-49a4-4001-be70-de6d36797945
  spec:
    sourcePod: network-check-source-dbd9cf844-rdvxr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:38:31Z"
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306731ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:45:31Z"
    - latency: 2.781862ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:44:31Z"
    - latency: 2.346242ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 2.061923ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 2.499963ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 2.008983ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 2.291156ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:39:31Z"
    - latency: 2.252786ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:38:31Z"
    - latency: 2.259661ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:37:31Z"
    - latency: 2.322776ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:31:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-113-to-network-check-target-ip-10-0-138-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-113.ec2.internal
      uid: 911c686d-2d7f-4485-83d2-248b43aef371
    resourceVersion: "16703"
    uid: cba6df4d-d254-415d-9e8d-43a5ffbd4d18
  spec:
    sourcePod: network-check-source-dbd9cf844-rdvxr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:38:31Z"
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.164487ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:45:31Z"
    - latency: 2.508471ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:44:31Z"
    - latency: 2.089134ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 2.144402ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 2.376682ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 2.167595ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 2.210706ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:39:31Z"
    - latency: 2.476399ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:38:31Z"
    - latency: 2.382264ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:37:31Z"
    - latency: 2.336573ms
      message: 'network-check-target-ip-10-0-138-235: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:31:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-113-to-network-check-target-ip-10-0-141-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-113.ec2.internal
      uid: 911c686d-2d7f-4485-83d2-248b43aef371
    resourceVersion: "16702"
    uid: 61141822-60be-4558-bf9c-ccf1383c4b1c
  spec:
    sourcePod: network-check-source-dbd9cf844-rdvxr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:38:31Z"
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.079µs
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:45:31Z"
    - latency: 913.652µs
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:44:31Z"
    - latency: 980.501µs
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 1.109684ms
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 985.03µs
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 1.065991ms
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 899.06µs
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:39:31Z"
    - latency: 811.552µs
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:38:31Z"
    - latency: 1.283105ms
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:37:31Z"
    - latency: 899.671µs
      message: 'network-check-target-ip-10-0-141-113: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:36:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T18:31:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-113-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-113.ec2.internal
      uid: 911c686d-2d7f-4485-83d2-248b43aef371
    resourceVersion: "15948"
    uid: 624edb91-e8e7-47cc-babd-b496bf4a9634
  spec:
    sourcePod: network-check-source-dbd9cf844-rdvxr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T18:37:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.114548ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 1.924465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:43:31Z"
    - latency: 723.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 1.847989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:42:31Z"
    - latency: 910.86µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 1.858008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:41:31Z"
    - latency: 820.573µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 1.658824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:40:31Z"
    - latency: 753.393µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T18:39:31Z"
    - latency: 1.707844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T18:39:31Z"
kind: List
metadata:
  resourceVersion: ""