apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-198-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-198.ec2.internal
      uid: 3cda94d1-eadb-4ca5-9a16-521950759981
    resourceVersion: "71328"
    uid: 8d6ff60a-2535-4f89-b4c3-786921262efd
  spec:
    sourcePod: network-check-source-65bdbbff45-4cgml
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:37:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.107µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:19:37Z"
    - latency: 1.316352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:18:37Z"
    - latency: 1.19717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:17:37Z"
    - latency: 934.312µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:16:37Z"
    - latency: 907.697µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:15:37Z"
    - latency: 1.343933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:14:37Z"
    - latency: 1.203218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:13:37Z"
    - latency: 1.207048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:12:37Z"
    - latency: 1.260561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:11:37Z"
    - latency: 947.502µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:10:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-198-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-198.ec2.internal
      uid: 3cda94d1-eadb-4ca5-9a16-521950759981
    resourceVersion: "76675"
    uid: 6f96df13-b809-47cd-9b1f-b775579459b6
  spec:
    sourcePod: network-check-source-65bdbbff45-4cgml
    targetEndpoint: a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:36:37Z"
      message: 'load-balancer-api-external: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.807282ms
      message: 'load-balancer-api-external: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:24:37Z"
    - latency: 7.530463ms
      message: 'load-balancer-api-external: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:24:37Z"
    - latency: 5.282747ms
      message: 'load-balancer-api-external: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:23:37Z"
    - latency: 6.37475ms
      message: 'load-balancer-api-external: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:23:37Z"
    - latency: 5.280445ms
      message: 'load-balancer-api-external: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:22:37Z"
    - latency: 10.179482ms
      message: 'load-balancer-api-external: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:22:37Z"
    - latency: 4.929564ms
      message: 'load-balancer-api-external: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:21:37Z"
    - latency: 10.157445ms
      message: 'load-balancer-api-external: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:21:37Z"
    - latency: 4.495226ms
      message: 'load-balancer-api-external: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:20:37Z"
    - latency: 7.400577ms
      message: 'load-balancer-api-external: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:20:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-198-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-198.ec2.internal
      uid: 3cda94d1-eadb-4ca5-9a16-521950759981
    resourceVersion: "76674"
    uid: eafba969-df81-4f1b-abcf-38a7d6bba258
  spec:
    sourcePod: network-check-source-65bdbbff45-4cgml
    targetEndpoint: a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:36:37Z"
      message: 'load-balancer-api-internal: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.724994ms
      message: 'load-balancer-api-internal: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:24:37Z"
    - latency: 7.562ms
      message: 'load-balancer-api-internal: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:24:37Z"
    - latency: 5.235117ms
      message: 'load-balancer-api-internal: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:23:37Z"
    - latency: 6.430899ms
      message: 'load-balancer-api-internal: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:23:37Z"
    - latency: 5.212422ms
      message: 'load-balancer-api-internal: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:22:37Z"
    - latency: 10.305866ms
      message: 'load-balancer-api-internal: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:22:37Z"
    - latency: 3.129208ms
      message: 'load-balancer-api-internal: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:21:37Z"
    - latency: 10.242012ms
      message: 'load-balancer-api-internal: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:21:37Z"
    - latency: 5.810312ms
      message: 'load-balancer-api-internal: tcp connection to a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:20:37Z"
    - latency: 7.477263ms
      message: 'load-balancer-api-internal: resolved host name a234ba043e40a4b8f9d21abcd191930a-60bfdb1ff2fb0751.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:20:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-198-to-network-check-target-ip-10-0-130-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-198.ec2.internal
      uid: 3cda94d1-eadb-4ca5-9a16-521950759981
    resourceVersion: "71326"
    uid: 4d11768b-470c-47d1-9a4b-9d788a87f416
  spec:
    sourcePod: network-check-source-65bdbbff45-4cgml
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:37:37Z"
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.239145ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:19:37Z"
    - latency: 2.074336ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:18:37Z"
    - latency: 1.818148ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:17:37Z"
    - latency: 2.105689ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:16:37Z"
    - latency: 1.778295ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:15:37Z"
    - latency: 2.142474ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:14:37Z"
    - latency: 2.101063ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:13:37Z"
    - latency: 2.162497ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:12:37Z"
    - latency: 2.156869ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:11:37Z"
    - latency: 1.848327ms
      message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:10:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-198-to-network-check-target-ip-10-0-139-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-198.ec2.internal
      uid: 3cda94d1-eadb-4ca5-9a16-521950759981
    resourceVersion: "71325"
    uid: 1b5cf9ed-ee59-47c7-b0f6-f3f23c3142c7
  spec:
    sourcePod: network-check-source-65bdbbff45-4cgml
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:37:37Z"
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.236751ms
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:19:37Z"
    - latency: 1.425815ms
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:18:37Z"
    - latency: 982.155µs
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:17:37Z"
    - latency: 1.14552ms
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:16:37Z"
    - latency: 1.194341ms
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:15:37Z"
    - latency: 1.220991ms
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:14:37Z"
    - latency: 785.64µs
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:13:37Z"
    - latency: 843.69µs
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:12:37Z"
    - latency: 929.377µs
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:11:37Z"
    - latency: 948.664µs
      message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:10:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-198-to-network-check-target-ip-10-0-142-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-198.ec2.internal
      uid: 3cda94d1-eadb-4ca5-9a16-521950759981
    resourceVersion: "71327"
    uid: 222be68e-9c84-4c39-935c-f6b053cd01a7
  spec:
    sourcePod: network-check-source-65bdbbff45-4cgml
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:37:37Z"
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.336728ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:19:37Z"
    - latency: 2.252056ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:18:37Z"
    - latency: 2.077498ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:17:37Z"
    - latency: 2.087358ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:16:37Z"
    - latency: 2.11224ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:15:37Z"
    - latency: 2.102689ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:14:37Z"
    - latency: 2.042618ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:13:37Z"
    - latency: 2.464237ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:12:37Z"
    - latency: 2.304053ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:11:37Z"
    - latency: 2.224023ms
      message: 'network-check-target-ip-10-0-142-113: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:10:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T10:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-198-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-198.ec2.internal
      uid: 3cda94d1-eadb-4ca5-9a16-521950759981
    resourceVersion: "76673"
    uid: bb36159a-fef3-4c11-ba3d-05d6ce85e81c
  spec:
    sourcePod: network-check-source-65bdbbff45-4cgml
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T10:36:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.138504ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:24:37Z"
    - latency: 1.776623ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:24:37Z"
    - latency: 886.082µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:23:37Z"
    - latency: 1.798481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:23:37Z"
    - latency: 1.102416ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:22:37Z"
    - latency: 2.147444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:22:37Z"
    - latency: 1.058516ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:21:37Z"
    - latency: 1.64795ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:21:37Z"
    - latency: 1.093831ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T11:20:37Z"
    - latency: 2.137988ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T11:20:37Z"
kind: List
metadata:
  resourceVersion: ""