apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T01:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-23.ec2.internal
      uid: 744f0334-a638-4690-b682-de313ecb5cb8
    resourceVersion: "53273"
    uid: 4f35b208-f9ca-4099-8cb2-550edf31be56
  spec:
    sourcePod: network-check-source-685456655f-52s8j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:18:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.20429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 1.186545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 1.480269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:37:57Z"
    - latency: 1.119613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:36:57Z"
    - latency: 1.048666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:35:57Z"
    - latency: 761.32µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:34:57Z"
    - latency: 894.152µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:33:57Z"
    - latency: 873.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:32:57Z"
    - latency: 1.171397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:31:57Z"
    - latency: 1.069579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:30:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T01:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-23.ec2.internal
      uid: 744f0334-a638-4690-b682-de313ecb5cb8
    resourceVersion: "55258"
    uid: e24e7b1c-4b48-4d92-91b1-fce883adc867
  spec:
    sourcePod: network-check-source-685456655f-52s8j
    targetEndpoint: a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:17:57Z"
      message: 'load-balancer-api-external: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.807981ms
      message: 'load-balancer-api-external: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:41:57Z"
    - latency: 6.54939ms
      message: 'load-balancer-api-external: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:41:57Z"
    - latency: 3.953224ms
      message: 'load-balancer-api-external: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:40:57Z"
    - latency: 6.955501ms
      message: 'load-balancer-api-external: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:40:57Z"
    - latency: 3.783306ms
      message: 'load-balancer-api-external: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 6.056977ms
      message: 'load-balancer-api-external: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 4.472841ms
      message: 'load-balancer-api-external: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 7.448658ms
      message: 'load-balancer-api-external: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 4.330547ms
      message: 'load-balancer-api-external: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:37:57Z"
    - latency: 7.136644ms
      message: 'load-balancer-api-external: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:37:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T01:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-23.ec2.internal
      uid: 744f0334-a638-4690-b682-de313ecb5cb8
    resourceVersion: "55259"
    uid: c118d6c1-f521-4809-9b32-680622ae669b
  spec:
    sourcePod: network-check-source-685456655f-52s8j
    targetEndpoint: a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:17:57Z"
      message: 'load-balancer-api-internal: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.724863ms
      message: 'load-balancer-api-internal: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:41:57Z"
    - latency: 6.616432ms
      message: 'load-balancer-api-internal: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:41:57Z"
    - latency: 4.24587ms
      message: 'load-balancer-api-internal: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:40:57Z"
    - latency: 6.894846ms
      message: 'load-balancer-api-internal: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:40:57Z"
    - latency: 3.786066ms
      message: 'load-balancer-api-internal: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 6.223393ms
      message: 'load-balancer-api-internal: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 4.488396ms
      message: 'load-balancer-api-internal: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 7.403326ms
      message: 'load-balancer-api-internal: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 4.127874ms
      message: 'load-balancer-api-internal: tcp connection to a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:37:57Z"
    - latency: 7.218332ms
      message: 'load-balancer-api-internal: resolved host name a4bfb62a6ba4b4a83b4097d8b70a5c30-b929812b9e008a9a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:37:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T01:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-129-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-23.ec2.internal
      uid: 744f0334-a638-4690-b682-de313ecb5cb8
    resourceVersion: "53270"
    uid: 3c8ded5f-cc6d-445c-a8f2-6f5f3db99334
  spec:
    sourcePod: network-check-source-685456655f-52s8j
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:18:57Z"
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.578413ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 988.903µs
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 914.403µs
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:37:57Z"
    - latency: 1.02677ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:36:57Z"
    - latency: 1.189397ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:35:57Z"
    - latency: 931.017µs
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:34:57Z"
    - latency: 1.18834ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:33:57Z"
    - latency: 1.430967ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:32:57Z"
    - latency: 1.019224ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:31:57Z"
    - latency: 957.744µs
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:30:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T01:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-132-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-23.ec2.internal
      uid: 744f0334-a638-4690-b682-de313ecb5cb8
    resourceVersion: "53271"
    uid: 143d9594-19e2-4cbf-8eaa-89ce400d7048
  spec:
    sourcePod: network-check-source-685456655f-52s8j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:18:57Z"
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.58101ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 2.174779ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 2.374994ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:37:57Z"
    - latency: 1.995068ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:36:57Z"
    - latency: 2.589105ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:35:57Z"
    - latency: 2.434428ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:34:57Z"
    - latency: 2.397785ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:33:57Z"
    - latency: 2.210804ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:32:57Z"
    - latency: 2.275797ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:31:57Z"
    - latency: 2.122286ms
      message: 'network-check-target-ip-10-0-132-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:30:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T01:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-132-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-23.ec2.internal
      uid: 744f0334-a638-4690-b682-de313ecb5cb8
    resourceVersion: "53272"
    uid: e29398c5-01f7-4a3b-b901-b6f658934f2b
  spec:
    sourcePod: network-check-source-685456655f-52s8j
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:18:57Z"
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.380234ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 2.088399ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 1.982779ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:37:57Z"
    - latency: 2.030203ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:36:57Z"
    - latency: 1.992285ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:35:57Z"
    - latency: 2.034959ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:34:57Z"
    - latency: 2.304687ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:33:57Z"
    - latency: 2.288822ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:32:57Z"
    - latency: 2.431333ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:31:57Z"
    - latency: 1.890208ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:30:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T01:11:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-23.ec2.internal
      uid: 744f0334-a638-4690-b682-de313ecb5cb8
    resourceVersion: "55257"
    uid: 7cb28b68-79a1-42af-9b93-ced5142451bc
  spec:
    sourcePod: network-check-source-685456655f-52s8j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:17:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148387ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:41:57Z"
    - latency: 1.915898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:41:57Z"
    - latency: 875.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:40:57Z"
    - latency: 1.719788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:40:57Z"
    - latency: 1.029484ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 1.578092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:39:57Z"
    - latency: 1.076845ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 1.836645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:38:57Z"
    - latency: 987.205µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:37:57Z"
    - latency: 1.948441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:37:57Z"
kind: List
metadata:
  resourceVersion: ""