apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:40:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-151-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-151.ec2.internal
      uid: 3288c0e4-bc98-49cb-8eff-6f3c6ef9baf0
    resourceVersion: "58676"
    uid: 7995af0a-4265-4f3c-b259-fb8601973988
  spec:
    sourcePod: network-check-source-6f8b768455-gxgl2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:47:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.712285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 1.046773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 1.25816ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:44Z"
    - latency: 1.318653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:44Z"
    - latency: 1.851812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:44Z"
    - latency: 1.036498ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:44Z"
    - latency: 1.125203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:44Z"
    - latency: 1.499461ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:44Z"
    - latency: 1.427991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:44Z"
    - latency: 1.692311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:40:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-151-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-151.ec2.internal
      uid: 3288c0e4-bc98-49cb-8eff-6f3c6ef9baf0
    resourceVersion: "60184"
    uid: 5a50b5e4-605e-4dae-8872-986d8469b152
  spec:
    sourcePod: network-check-source-6f8b768455-gxgl2
    targetEndpoint: a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:44Z"
      message: 'load-balancer-api-external: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.13825ms
      message: 'load-balancer-api-external: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:10:44Z"
    - latency: 8.97965ms
      message: 'load-balancer-api-external: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:10:44Z"
    - latency: 6.268819ms
      message: 'load-balancer-api-external: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:44Z"
    - latency: 8.411636ms
      message: 'load-balancer-api-external: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:44Z"
    - latency: 5.800415ms
      message: 'load-balancer-api-external: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 8.175445ms
      message: 'load-balancer-api-external: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 5.119039ms
      message: 'load-balancer-api-external: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 8.528544ms
      message: 'load-balancer-api-external: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 5.482912ms
      message: 'load-balancer-api-external: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:44Z"
    - latency: 6.549103ms
      message: 'load-balancer-api-external: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:40:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-151-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-151.ec2.internal
      uid: 3288c0e4-bc98-49cb-8eff-6f3c6ef9baf0
    resourceVersion: "60185"
    uid: 69197bfc-05dd-41d6-92a3-aafd4353fb12
  spec:
    sourcePod: network-check-source-6f8b768455-gxgl2
    targetEndpoint: a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:44Z"
      message: 'load-balancer-api-internal: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.148654ms
      message: 'load-balancer-api-internal: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:10:44Z"
    - latency: 8.955823ms
      message: 'load-balancer-api-internal: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:10:44Z"
    - latency: 6.29944ms
      message: 'load-balancer-api-internal: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:44Z"
    - latency: 8.388126ms
      message: 'load-balancer-api-internal: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:44Z"
    - latency: 5.754335ms
      message: 'load-balancer-api-internal: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 8.102538ms
      message: 'load-balancer-api-internal: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 5.063994ms
      message: 'load-balancer-api-internal: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 8.456555ms
      message: 'load-balancer-api-internal: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 5.49374ms
      message: 'load-balancer-api-internal: tcp connection to a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:44Z"
    - latency: 6.539803ms
      message: 'load-balancer-api-internal: resolved host name a15ee7a615afa4603913bb50b57d513d-bbd3d7b9467311bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:40:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-151-to-network-check-target-ip-10-0-128-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-151.ec2.internal
      uid: 3288c0e4-bc98-49cb-8eff-6f3c6ef9baf0
    resourceVersion: "58675"
    uid: 2e18073d-e170-45b7-9f4b-557800261eed
  spec:
    sourcePod: network-check-source-6f8b768455-gxgl2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:47:44Z"
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.51684ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 2.268797ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 2.435037ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:44Z"
    - latency: 2.625746ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:44Z"
    - latency: 2.66962ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:44Z"
    - latency: 3.140339ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:44Z"
    - latency: 2.686194ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:44Z"
    - latency: 3.131101ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:44Z"
    - latency: 2.60727ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:44Z"
    - latency: 3.450842ms
      message: 'network-check-target-ip-10-0-128-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:40:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-151-to-network-check-target-ip-10-0-129-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-151.ec2.internal
      uid: 3288c0e4-bc98-49cb-8eff-6f3c6ef9baf0
    resourceVersion: "58673"
    uid: 3f83ab8a-9e80-4896-8cd6-52fd404f7c66
  spec:
    sourcePod: network-check-source-6f8b768455-gxgl2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:47:44Z"
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.10169ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 1.586359ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 1.048537ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:44Z"
    - latency: 1.282268ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:44Z"
    - latency: 1.189678ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:44Z"
    - latency: 1.386553ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:44Z"
    - latency: 1.124966ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:44Z"
    - latency: 1.49833ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:44Z"
    - latency: 1.235089ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:44Z"
    - latency: 1.502479ms
      message: 'network-check-target-ip-10-0-129-151: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:40:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-151-to-network-check-target-ip-10-0-134-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-151.ec2.internal
      uid: 3288c0e4-bc98-49cb-8eff-6f3c6ef9baf0
    resourceVersion: "58674"
    uid: 032b410d-08c7-4d05-b53d-3bafae136524
  spec:
    sourcePod: network-check-source-6f8b768455-gxgl2
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:47:44Z"
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.587651ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 2.724199ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 2.808869ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:44Z"
    - latency: 2.521482ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:44Z"
    - latency: 2.768567ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:44Z"
    - latency: 3.035291ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:44Z"
    - latency: 2.919543ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:44Z"
    - latency: 3.002347ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:44Z"
    - latency: 2.746864ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:44Z"
    - latency: 2.844669ms
      message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:40:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-151-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-151.ec2.internal
      uid: 3288c0e4-bc98-49cb-8eff-6f3c6ef9baf0
    resourceVersion: "60183"
    uid: 5fee26c7-9894-4262-97ff-f6788a34f9b9
  spec:
    sourcePod: network-check-source-6f8b768455-gxgl2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.053002ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:10:44Z"
    - latency: 2.357782ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:10:44Z"
    - latency: 1.448008ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:44Z"
    - latency: 2.147014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:44Z"
    - latency: 1.44432ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 2.374018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:44Z"
    - latency: 1.006562ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 2.160058ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:44Z"
    - latency: 1.041979ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:44Z"
    - latency: 1.982797ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:44Z"
kind: List
metadata:
  resourceVersion: ""