apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T22:35:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: cdec864c-c60d-438d-9696-9e9b512f8ec3
    resourceVersion: "54689"
    uid: b4387e81-24e7-4c3f-95d1-192e56555138
  spec:
    sourcePod: network-check-source-685456655f-p46w7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T22:42:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.188027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 974.595µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 1.559721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:01:32Z"
    - latency: 4.92096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:00:32Z"
    - latency: 1.051188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:59:32Z"
    - latency: 1.593556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:58:32Z"
    - latency: 1.387228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:57:32Z"
    - latency: 1.646453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:56:32Z"
    - latency: 924.562µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:55:32Z"
    - latency: 1.219232ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:54:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T22:35:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: cdec864c-c60d-438d-9696-9e9b512f8ec3
    resourceVersion: "56284"
    uid: 81b2aa29-548a-46e5-a1f4-03aeae26581d
  spec:
    sourcePod: network-check-source-685456655f-p46w7
    targetEndpoint: a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T22:41:32Z"
      message: 'load-balancer-api-external: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.148703ms
      message: 'load-balancer-api-external: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:05:32Z"
    - latency: 8.443222ms
      message: 'load-balancer-api-external: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:05:32Z"
    - latency: 4.542652ms
      message: 'load-balancer-api-external: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:04:32Z"
    - latency: 8.976254ms
      message: 'load-balancer-api-external: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:04:32Z"
    - latency: 6.096666ms
      message: 'load-balancer-api-external: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 7.668791ms
      message: 'load-balancer-api-external: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 4.278983ms
      message: 'load-balancer-api-external: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 8.526546ms
      message: 'load-balancer-api-external: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 5.171638ms
      message: 'load-balancer-api-external: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:01:32Z"
    - latency: 8.214078ms
      message: 'load-balancer-api-external: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:01:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T22:35:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: cdec864c-c60d-438d-9696-9e9b512f8ec3
    resourceVersion: "56285"
    uid: 6df17fc9-67b2-4aa1-81ee-7c1f7749828d
  spec:
    sourcePod: network-check-source-685456655f-p46w7
    targetEndpoint: a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T22:41:32Z"
      message: 'load-balancer-api-internal: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.07697ms
      message: 'load-balancer-api-internal: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:05:32Z"
    - latency: 8.339299ms
      message: 'load-balancer-api-internal: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:05:32Z"
    - latency: 4.363482ms
      message: 'load-balancer-api-internal: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:04:32Z"
    - latency: 9.03138ms
      message: 'load-balancer-api-internal: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:04:32Z"
    - latency: 4.576019ms
      message: 'load-balancer-api-internal: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 7.576336ms
      message: 'load-balancer-api-internal: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 4.285714ms
      message: 'load-balancer-api-internal: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 8.607488ms
      message: 'load-balancer-api-internal: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 5.25319ms
      message: 'load-balancer-api-internal: tcp connection to a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:01:32Z"
    - latency: 8.27323ms
      message: 'load-balancer-api-internal: resolved host name a5a6083b5a9f54eed9a8eca0f282ce8c-ec683ad392ba5cfd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:01:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T22:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-ip-10-0-137-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: cdec864c-c60d-438d-9696-9e9b512f8ec3
    resourceVersion: "54687"
    uid: 7dc9cee4-77ba-463f-ae52-62977b3e80bb
  spec:
    sourcePod: network-check-source-685456655f-p46w7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T22:42:32Z"
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.311218ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 2.716963ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 2.122808ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:01:32Z"
    - latency: 6.211081ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:00:32Z"
    - latency: 2.484437ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:59:32Z"
    - latency: 2.138886ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:58:32Z"
    - latency: 2.6519ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:57:32Z"
    - latency: 2.409267ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:56:32Z"
    - latency: 2.193148ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:55:32Z"
    - latency: 2.801879ms
      message: 'network-check-target-ip-10-0-137-80: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:54:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T22:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-ip-10-0-138-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: cdec864c-c60d-438d-9696-9e9b512f8ec3
    resourceVersion: "54688"
    uid: fa4f1d11-e652-4a5c-8293-33998995ef4e
  spec:
    sourcePod: network-check-source-685456655f-p46w7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T22:42:32Z"
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.309344ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 2.086195ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 2.549233ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:01:32Z"
    - latency: 8.275748ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:00:32Z"
    - latency: 2.476725ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:59:32Z"
    - latency: 3.045487ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:58:32Z"
    - latency: 2.575202ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:57:32Z"
    - latency: 2.845678ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:56:32Z"
    - latency: 2.298426ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:55:32Z"
    - latency: 2.466075ms
      message: 'network-check-target-ip-10-0-138-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:54:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T22:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-ip-10-0-143-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: cdec864c-c60d-438d-9696-9e9b512f8ec3
    resourceVersion: "54686"
    uid: 2e931e08-8323-48b6-9f47-286b04c4bc19
  spec:
    sourcePod: network-check-source-685456655f-p46w7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T22:42:32Z"
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.407µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 1.437315ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 1.382738ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:01:32Z"
    - latency: 1.671315ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:00:32Z"
    - latency: 1.421293ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:59:32Z"
    - latency: 957.986µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:58:32Z"
    - latency: 1.099781ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:57:32Z"
    - latency: 1.184106ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:56:32Z"
    - latency: 1.120801ms
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:55:32Z"
    - latency: 961.894µs
      message: 'network-check-target-ip-10-0-143-210: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T22:54:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T22:35:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-210-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-210.ec2.internal
      uid: cdec864c-c60d-438d-9696-9e9b512f8ec3
    resourceVersion: "56283"
    uid: 5ca00ab7-4cf6-4d37-aaa9-297da798eb69
  spec:
    sourcePod: network-check-source-685456655f-p46w7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T22:41:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.169509ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:05:32Z"
    - latency: 2.136786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:05:32Z"
    - latency: 933.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:04:32Z"
    - latency: 1.628954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:04:32Z"
    - latency: 1.14112ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 1.721161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:03:32Z"
    - latency: 1.330163ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 1.680556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:02:32Z"
    - latency: 1.275164ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T23:01:32Z"
    - latency: 2.126036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T23:01:32Z"
kind: List
metadata:
  resourceVersion: ""