apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:17:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-50-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-50.ec2.internal
      uid: 26e02831-2c65-422b-a2fd-fa1434d1dfcf
    resourceVersion: "67344"
    uid: 5dba972c-db15-419a-8b30-d74ccb0b168e
  spec:
    sourcePod: network-check-source-6f8b768455-st2qc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:24:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.056983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 1.18149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 974.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 1.184639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:49:59Z"
    - latency: 1.057735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:48:59Z"
    - latency: 1.17922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:59Z"
    - latency: 1.03751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:59Z"
    - latency: 1.666224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:59Z"
    - latency: 1.151402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:59Z"
    - latency: 877.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:17:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-50-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-50.ec2.internal
      uid: 26e02831-2c65-422b-a2fd-fa1434d1dfcf
    resourceVersion: "68316"
    uid: 52593d2f-61f9-44ac-b993-d56b1c1fe630
  spec:
    sourcePod: network-check-source-6f8b768455-st2qc
    targetEndpoint: a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:23:59Z"
      message: 'load-balancer-api-external: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.95245ms
      message: 'load-balancer-api-external: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:53:59Z"
    - latency: 8.408045ms
      message: 'load-balancer-api-external: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:53:59Z"
    - latency: 6.202145ms
      message: 'load-balancer-api-external: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 9.27245ms
      message: 'load-balancer-api-external: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 3.700582ms
      message: 'load-balancer-api-external: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 6.457382ms
      message: 'load-balancer-api-external: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 5.225575ms
      message: 'load-balancer-api-external: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 8.681951ms
      message: 'load-balancer-api-external: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 4.111241ms
      message: 'load-balancer-api-external: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:49:59Z"
    - latency: 8.631475ms
      message: 'load-balancer-api-external: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:49:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:17:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-50-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-50.ec2.internal
      uid: 26e02831-2c65-422b-a2fd-fa1434d1dfcf
    resourceVersion: "68315"
    uid: e511c114-744d-484e-984d-3f0201a91ca8
  spec:
    sourcePod: network-check-source-6f8b768455-st2qc
    targetEndpoint: a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:23:59Z"
      message: 'load-balancer-api-internal: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.020094ms
      message: 'load-balancer-api-internal: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:53:59Z"
    - latency: 8.485237ms
      message: 'load-balancer-api-internal: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:53:59Z"
    - latency: 5.519859ms
      message: 'load-balancer-api-internal: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 9.29589ms
      message: 'load-balancer-api-internal: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 3.662624ms
      message: 'load-balancer-api-internal: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 6.533332ms
      message: 'load-balancer-api-internal: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 5.211486ms
      message: 'load-balancer-api-internal: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 8.714973ms
      message: 'load-balancer-api-internal: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 4.201848ms
      message: 'load-balancer-api-internal: tcp connection to a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:49:59Z"
    - latency: 8.712486ms
      message: 'load-balancer-api-internal: resolved host name a78f719b4a40c4ba2984c6d3a2dc8110-43a3f22b7e921c03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:49:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:17:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-128-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-50.ec2.internal
      uid: 26e02831-2c65-422b-a2fd-fa1434d1dfcf
    resourceVersion: "67341"
    uid: 78e9ac2e-32df-4b0c-bfd6-854bacebacdc
  spec:
    sourcePod: network-check-source-6f8b768455-st2qc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:24:59Z"
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.453301ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 1.161376ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 1.085135ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 1.49909ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:49:59Z"
    - latency: 909.778µs
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:48:59Z"
    - latency: 969.417µs
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:59Z"
    - latency: 839.012µs
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:59Z"
    - latency: 1.195738ms
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:59Z"
    - latency: 945.313µs
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:59Z"
    - latency: 894.858µs
      message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:17:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-132-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-50.ec2.internal
      uid: 26e02831-2c65-422b-a2fd-fa1434d1dfcf
    resourceVersion: "67342"
    uid: 073b37ce-ef01-4ff4-8b5f-ae1f0bd43c62
  spec:
    sourcePod: network-check-source-6f8b768455-st2qc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:24:59Z"
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.507393ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 2.297461ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 2.308849ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 2.275721ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:49:59Z"
    - latency: 2.318114ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:48:59Z"
    - latency: 2.354334ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:59Z"
    - latency: 2.649446ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:59Z"
    - latency: 2.138985ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:59Z"
    - latency: 2.446622ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:59Z"
    - latency: 2.37496ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:17:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-132-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-50.ec2.internal
      uid: 26e02831-2c65-422b-a2fd-fa1434d1dfcf
    resourceVersion: "67343"
    uid: 7d5b30a1-737f-4cd7-9042-46b64119254f
  spec:
    sourcePod: network-check-source-6f8b768455-st2qc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:24:59Z"
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.882458ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 2.565781ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 2.518423ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 2.596411ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:49:59Z"
    - latency: 2.387306ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:48:59Z"
    - latency: 2.405266ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:47:59Z"
    - latency: 2.226592ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:46:59Z"
    - latency: 4.678095ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:45:59Z"
    - latency: 2.361516ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:44:59Z"
    - latency: 2.492581ms
      message: 'network-check-target-ip-10-0-132-217: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:43:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T14:17:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-50-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-50.ec2.internal
      uid: 26e02831-2c65-422b-a2fd-fa1434d1dfcf
    resourceVersion: "68314"
    uid: fad0a137-7dd8-4687-815b-c0a39e2a44f3
  spec:
    sourcePod: network-check-source-6f8b768455-st2qc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T14:23:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:53:59Z"
    - latency: 1.709982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:53:59Z"
    - latency: 1.179951ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 1.906653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:52:59Z"
    - latency: 1.102868ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 1.821707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:51:59Z"
    - latency: 1.115336ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 1.744158ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:50:59Z"
    - latency: 834.402µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:49:59Z"
    - latency: 2.007746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:49:59Z"
kind: List
metadata:
  resourceVersion: ""