apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-21.ec2.internal
      uid: 0539f215-31cd-466c-b38b-c5a592e360c8
    resourceVersion: "95230"
    uid: 1e47b0c1-f592-4702-b055-3343c591d73e
  spec:
    sourcePod: network-check-source-6f78d59f99-52vqt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:29:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.241592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 890.839µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 1.337047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 1.054225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 964.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:25Z"
    - latency: 970.395µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:25Z"
    - latency: 1.283539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:25Z"
    - latency: 1.122575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:25Z"
    - latency: 3.36698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:25Z"
    - latency: 1.387172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-21.ec2.internal
      uid: 0539f215-31cd-466c-b38b-c5a592e360c8
    resourceVersion: "95231"
    uid: ce9653e7-d0ec-4916-8916-84ed4e31b1ef
  spec:
    sourcePod: network-check-source-6f78d59f99-52vqt
    targetEndpoint: a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:28:25Z"
      message: 'load-balancer-api-external: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.056349ms
      message: 'load-balancer-api-external: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 7.151222ms
      message: 'load-balancer-api-external: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 18.081956ms
      message: 'load-balancer-api-external: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 7.365817ms
      message: 'load-balancer-api-external: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 17.32444ms
      message: 'load-balancer-api-external: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 6.915875ms
      message: 'load-balancer-api-external: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 18.207648ms
      message: 'load-balancer-api-external: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 7.902027ms
      message: 'load-balancer-api-external: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 16.855095ms
      message: 'load-balancer-api-external: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:25Z"
    - latency: 6.534492ms
      message: 'load-balancer-api-external: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:00:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-21.ec2.internal
      uid: 0539f215-31cd-466c-b38b-c5a592e360c8
    resourceVersion: "95232"
    uid: f9d11fe3-1f70-4bdb-8b27-dc7572830667
  spec:
    sourcePod: network-check-source-6f78d59f99-52vqt
    targetEndpoint: a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:28:25Z"
      message: 'load-balancer-api-internal: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.027436ms
      message: 'load-balancer-api-internal: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 7.121551ms
      message: 'load-balancer-api-internal: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 18.276077ms
      message: 'load-balancer-api-internal: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 7.279284ms
      message: 'load-balancer-api-internal: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 17.687565ms
      message: 'load-balancer-api-internal: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 6.872417ms
      message: 'load-balancer-api-internal: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 17.654074ms
      message: 'load-balancer-api-internal: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 7.83291ms
      message: 'load-balancer-api-internal: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 16.726698ms
      message: 'load-balancer-api-internal: tcp connection to a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:25Z"
    - latency: 6.589618ms
      message: 'load-balancer-api-internal: resolved host name a787a0591887d423eb9a13ded70f7821-b6c85191bdf3de11.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:00:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-21-to-network-check-target-ip-10-0-132-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-21.ec2.internal
      uid: 0539f215-31cd-466c-b38b-c5a592e360c8
    resourceVersion: "95227"
    uid: 544dacfc-c262-4cea-83bf-0a7cee92782b
  spec:
    sourcePod: network-check-source-6f78d59f99-52vqt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:29:25Z"
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.78368ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 1.892375ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 1.892305ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 1.801414ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 1.891123ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:25Z"
    - latency: 1.554145ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:25Z"
    - latency: 1.826386ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:25Z"
    - latency: 2.118315ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:25Z"
    - latency: 11.347465ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:25Z"
    - latency: 1.764316ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-21-to-network-check-target-ip-10-0-138-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-21.ec2.internal
      uid: 0539f215-31cd-466c-b38b-c5a592e360c8
    resourceVersion: "95226"
    uid: 8adf3425-2177-4e1a-8c82-6070772908db
  spec:
    sourcePod: network-check-source-6f78d59f99-52vqt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:29:25Z"
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.434295ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 1.374678ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 1.341383ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 977.928µs
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 876.087µs
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:25Z"
    - latency: 870.711µs
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:25Z"
    - latency: 861.596µs
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:25Z"
    - latency: 910.019µs
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:25Z"
    - latency: 11.438239ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:25Z"
    - latency: 1.561396ms
      message: 'network-check-target-ip-10-0-138-21: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-21-to-network-check-target-ip-10-0-140-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-21.ec2.internal
      uid: 0539f215-31cd-466c-b38b-c5a592e360c8
    resourceVersion: "95228"
    uid: 61b1b46f-8131-4fcd-a838-8053c3921046
  spec:
    sourcePod: network-check-source-6f78d59f99-52vqt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:29:25Z"
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.48118ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 2.29786ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 2.460176ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 2.261663ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 2.463436ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:25Z"
    - latency: 2.025659ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:59:25Z"
    - latency: 2.131083ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:58:25Z"
    - latency: 2.119882ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:57:25Z"
    - latency: 11.530356ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:56:25Z"
    - latency: 3.035763ms
      message: 'network-check-target-ip-10-0-140-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:22:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-21.ec2.internal
      uid: 0539f215-31cd-466c-b38b-c5a592e360c8
    resourceVersion: "95229"
    uid: 7044f208-1661-4056-bc95-f4503065c73c
  spec:
    sourcePod: network-check-source-6f78d59f99-52vqt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:28:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 775.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 2.244971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:04:25Z"
    - latency: 1.0981ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 2.144619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:03:25Z"
    - latency: 1.292737ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 1.683394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:02:25Z"
    - latency: 980.298µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 2.342648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:01:25Z"
    - latency: 1.587393ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:00:25Z"
    - latency: 1.962357ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:00:25Z"
kind: List
metadata:
  resourceVersion: ""