apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 5a25db6f-8896-4dc3-aa6e-83897579197d
    resourceVersion: "63156"
    uid: 7473c0a8-014b-4f37-87ca-c7c2e1499e3d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-stvbm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:43:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.249µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 1.545321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 1.200741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 950.505µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 808.455µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:14:49Z"
    - latency: 1.33748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:13:49Z"
    - latency: 1.221324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:12:49Z"
    - latency: 1.374987ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:11:49Z"
    - latency: 1.200976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:10:49Z"
    - latency: 1.167741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 5a25db6f-8896-4dc3-aa6e-83897579197d
    resourceVersion: "63157"
    uid: f538ccd4-4d0a-481a-8e0d-3e2fc9d153bc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-stvbm
    targetEndpoint: a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:42:49Z"
      message: 'load-balancer-api-external: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.489909ms
      message: 'load-balancer-api-external: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 7.401443ms
      message: 'load-balancer-api-external: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 4.422287ms
      message: 'load-balancer-api-external: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 6.744114ms
      message: 'load-balancer-api-external: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 4.701097ms
      message: 'load-balancer-api-external: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 7.728884ms
      message: 'load-balancer-api-external: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 5.395397ms
      message: 'load-balancer-api-external: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 7.819479ms
      message: 'load-balancer-api-external: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 4.001156ms
      message: 'load-balancer-api-external: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:14:49Z"
    - latency: 8.620041ms
      message: 'load-balancer-api-external: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:14:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 5a25db6f-8896-4dc3-aa6e-83897579197d
    resourceVersion: "63158"
    uid: 4473997b-721c-4ace-b9e5-f0c7d27e4f78
  spec:
    sourcePod: network-check-source-7bc5b6bf85-stvbm
    targetEndpoint: a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:42:49Z"
      message: 'load-balancer-api-internal: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.749605ms
      message: 'load-balancer-api-internal: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 7.479905ms
      message: 'load-balancer-api-internal: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 4.446087ms
      message: 'load-balancer-api-internal: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 6.663505ms
      message: 'load-balancer-api-internal: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 4.701955ms
      message: 'load-balancer-api-internal: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 7.679731ms
      message: 'load-balancer-api-internal: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 5.391147ms
      message: 'load-balancer-api-internal: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 7.728613ms
      message: 'load-balancer-api-internal: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 4.013427ms
      message: 'load-balancer-api-internal: tcp connection to a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:14:49Z"
    - latency: 8.678336ms
      message: 'load-balancer-api-internal: resolved host name a5d156f4000b3442d92386d62b6131f6-111e0f1f51fb7dce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:14:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-131-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 5a25db6f-8896-4dc3-aa6e-83897579197d
    resourceVersion: "63154"
    uid: c0dbcbba-e2e5-4e6b-91c2-2f6b779022b3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-stvbm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:43:49Z"
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.258317ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 2.267309ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 2.232568ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 2.362161ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 2.382716ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:14:49Z"
    - latency: 2.17335ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:13:49Z"
    - latency: 2.353343ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:12:49Z"
    - latency: 2.474347ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:11:49Z"
    - latency: 2.309957ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:10:49Z"
    - latency: 2.358497ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-135-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 5a25db6f-8896-4dc3-aa6e-83897579197d
    resourceVersion: "63152"
    uid: 38d411a9-cc0a-4558-b85e-4d5887d1ff3e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-stvbm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:43:49Z"
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.395552ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 1.191053ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 971.637µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 879.014µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 967.227µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:14:49Z"
    - latency: 1.491922ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:13:49Z"
    - latency: 944.101µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:12:49Z"
    - latency: 1.547634ms
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:11:49Z"
    - latency: 966.055µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:10:49Z"
    - latency: 900.238µs
      message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-ip-10-0-140-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 5a25db6f-8896-4dc3-aa6e-83897579197d
    resourceVersion: "63153"
    uid: 6fddc84e-3459-4494-978d-3686f258b733
  spec:
    sourcePod: network-check-source-7bc5b6bf85-stvbm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:43:49Z"
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.04136ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 2.099525ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 2.107361ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 2.045717ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 1.949278ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:14:49Z"
    - latency: 1.889915ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:13:49Z"
    - latency: 1.881764ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:12:49Z"
    - latency: 2.007358ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:11:49Z"
    - latency: 2.048269ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:10:49Z"
    - latency: 2.02548ms
      message: 'network-check-target-ip-10-0-140-200: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:09:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T20:36:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-240-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-240.ec2.internal
      uid: 5a25db6f-8896-4dc3-aa6e-83897579197d
    resourceVersion: "63155"
    uid: 92c4b9c8-f327-4fe7-ab42-4c122175eb51
  spec:
    sourcePod: network-check-source-7bc5b6bf85-stvbm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T20:42:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.168126ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 1.714998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:18:49Z"
    - latency: 1.053782ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 1.835224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:17:49Z"
    - latency: 949.85µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 2.045733ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:16:49Z"
    - latency: 1.115392ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 1.656779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:15:49Z"
    - latency: 944.238µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T21:14:49Z"
    - latency: 1.807272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T21:14:49Z"
kind: List
metadata:
  resourceVersion: ""