apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T08:51:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-255-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-255.ec2.internal
      uid: ab359e61-7b3f-47bd-b2de-b40be0df17da
    resourceVersion: "30098"
    uid: aa2b525b-bb3a-4211-a6ac-024e1e4f78ff
  spec:
    sourcePod: network-check-source-56d84b9f44-dwrjc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T08:58:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:05:50Z"
    - latency: 1.089444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:04:50Z"
    - latency: 1.100116ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 991.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 956.588µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 922.503µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 1.481746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:59:50Z"
    - latency: 1.101136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:58:50Z"
    - latency: 990.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:57:50Z"
    - latency: 1.694181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T08:51:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-255-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-255.ec2.internal
      uid: ab359e61-7b3f-47bd-b2de-b40be0df17da
    resourceVersion: "28575"
    uid: e0bc2b45-2427-452d-91a4-3b2921d6cb0c
  spec:
    sourcePod: network-check-source-56d84b9f44-dwrjc
    targetEndpoint: aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T08:57:50Z"
      message: 'load-balancer-api-external: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.530279ms
      message: 'load-balancer-api-external: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 8.987887ms
      message: 'load-balancer-api-external: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 5.32803ms
      message: 'load-balancer-api-external: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 8.785031ms
      message: 'load-balancer-api-external: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 3.943599ms
      message: 'load-balancer-api-external: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 8.357498ms
      message: 'load-balancer-api-external: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 4.72925ms
      message: 'load-balancer-api-external: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 8.504907ms
      message: 'load-balancer-api-external: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 5.474996ms
      message: 'load-balancer-api-external: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:59:50Z"
    - latency: 8.100644ms
      message: 'load-balancer-api-external: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T08:59:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T08:51:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-255-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-255.ec2.internal
      uid: ab359e61-7b3f-47bd-b2de-b40be0df17da
    resourceVersion: "28576"
    uid: 6a1aa409-fd70-46a6-a175-00474b049e6a
  spec:
    sourcePod: network-check-source-56d84b9f44-dwrjc
    targetEndpoint: aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T08:57:50Z"
      message: 'load-balancer-api-internal: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.571252ms
      message: 'load-balancer-api-internal: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 9.102361ms
      message: 'load-balancer-api-internal: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 5.267529ms
      message: 'load-balancer-api-internal: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 8.84338ms
      message: 'load-balancer-api-internal: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 3.893551ms
      message: 'load-balancer-api-internal: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 8.475587ms
      message: 'load-balancer-api-internal: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 4.628769ms
      message: 'load-balancer-api-internal: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 8.536457ms
      message: 'load-balancer-api-internal: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 5.46412ms
      message: 'load-balancer-api-internal: tcp connection to aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:59:50Z"
    - latency: 8.164738ms
      message: 'load-balancer-api-internal: resolved host name aa52748401a384414ab9cb027b5c436e-ee229d32399f71d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T08:59:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T08:51:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-255-to-network-check-target-ip-10-0-129-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-255.ec2.internal
      uid: ab359e61-7b3f-47bd-b2de-b40be0df17da
    resourceVersion: "30096"
    uid: 319f90e6-d7cd-4a92-a739-60c4c189d5e6
  spec:
    sourcePod: network-check-source-56d84b9f44-dwrjc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T08:58:50Z"
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.255164ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:05:50Z"
    - latency: 2.295181ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:04:50Z"
    - latency: 2.051096ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 2.127242ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 2.216817ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 2.06033ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 2.364247ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:59:50Z"
    - latency: 2.184119ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:58:50Z"
    - latency: 2.164286ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:57:50Z"
    - latency: 2.110789ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T08:51:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-255-to-network-check-target-ip-10-0-130-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-255.ec2.internal
      uid: ab359e61-7b3f-47bd-b2de-b40be0df17da
    resourceVersion: "30095"
    uid: 11b86386-3c6b-46d4-926d-d2909602e392
  spec:
    sourcePod: network-check-source-56d84b9f44-dwrjc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T08:58:50Z"
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.606µs
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:05:50Z"
    - latency: 1.303728ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:04:50Z"
    - latency: 1.263865ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 900.562µs
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 1.246421ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 920.039µs
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 1.676782ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:59:50Z"
    - latency: 829.984µs
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:58:50Z"
    - latency: 1.175842ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:57:50Z"
    - latency: 1.451606ms
      message: 'network-check-target-ip-10-0-130-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T08:51:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-255-to-network-check-target-ip-10-0-138-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-255.ec2.internal
      uid: ab359e61-7b3f-47bd-b2de-b40be0df17da
    resourceVersion: "30097"
    uid: ea2d1c28-e4a9-4842-8519-c2e7327a9e46
  spec:
    sourcePod: network-check-source-56d84b9f44-dwrjc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T08:58:50Z"
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.227682ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:05:50Z"
    - latency: 2.128727ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:04:50Z"
    - latency: 1.976996ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 2.222385ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 1.758833ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 2.600546ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 3.76016ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:59:50Z"
    - latency: 2.117758ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:58:50Z"
    - latency: 2.720623ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:57:50Z"
    - latency: 2.921438ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T08:51:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-255-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-255.ec2.internal
      uid: ab359e61-7b3f-47bd-b2de-b40be0df17da
    resourceVersion: "28574"
    uid: 5a829690-4a0a-4547-8196-faca166020a3
  spec:
    sourcePod: network-check-source-56d84b9f44-dwrjc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T08:57:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 757.021µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 1.731221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:03:50Z"
    - latency: 777.318µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 1.628148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:02:50Z"
    - latency: 941.737µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 1.560076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:01:50Z"
    - latency: 1.246029ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 1.541948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T09:00:50Z"
    - latency: 969.842µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T08:59:50Z"
    - latency: 1.801267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T08:59:50Z"
kind: List
metadata:
  resourceVersion: ""