apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:19:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-105.ec2.internal
      uid: afb07787-6716-499c-b776-760f27c58867
    resourceVersion: "68877"
    uid: 6d4f980a-cef8-49c8-ae2c-b0175d0f3e64
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4m4wn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:26: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.237447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:08:57Z"
    - latency: 952.494µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 1.266721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 1.397105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 1.136373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 1.288076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:03:57Z"
    - latency: 1.300908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:57Z"
    - latency: 1.022302ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:57Z"
    - latency: 1.266471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:57Z"
    - latency: 846.526µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:19:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-105.ec2.internal
      uid: afb07787-6716-499c-b776-760f27c58867
    resourceVersion: "67906"
    uid: cf22bd1e-c065-4b39-aebb-8aecbf736e98
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4m4wn
    targetEndpoint: ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:25:57Z"
      message: 'load-balancer-api-external: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.678659ms
      message: 'load-balancer-api-external: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 9.379722ms
      message: 'load-balancer-api-external: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 5.790846ms
      message: 'load-balancer-api-external: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 8.370917ms
      message: 'load-balancer-api-external: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 5.534503ms
      message: 'load-balancer-api-external: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 9.228497ms
      message: 'load-balancer-api-external: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 3.18361ms
      message: 'load-balancer-api-external: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 8.667175ms
      message: 'load-balancer-api-external: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 4.607947ms
      message: 'load-balancer-api-external: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:03:57Z"
    - latency: 8.97898ms
      message: 'load-balancer-api-external: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:03:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:19:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-105.ec2.internal
      uid: afb07787-6716-499c-b776-760f27c58867
    resourceVersion: "67907"
    uid: 6ebf7d4f-88f9-4722-a495-ca7e15ce5874
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4m4wn
    targetEndpoint: ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:25:57Z"
      message: 'load-balancer-api-internal: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.641113ms
      message: 'load-balancer-api-internal: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 9.428113ms
      message: 'load-balancer-api-internal: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 5.791919ms
      message: 'load-balancer-api-internal: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 8.44732ms
      message: 'load-balancer-api-internal: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 5.537616ms
      message: 'load-balancer-api-internal: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 9.263406ms
      message: 'load-balancer-api-internal: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 4.565068ms
      message: 'load-balancer-api-internal: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 8.767409ms
      message: 'load-balancer-api-internal: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 4.685058ms
      message: 'load-balancer-api-internal: tcp connection to ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:03:57Z"
    - latency: 9.031351ms
      message: 'load-balancer-api-internal: resolved host name ab5a7624716964b908d949ca870eb2cc-5cbf0c8e93c16c0d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:03:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:19:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-105-to-network-check-target-ip-10-0-136-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-105.ec2.internal
      uid: afb07787-6716-499c-b776-760f27c58867
    resourceVersion: "68875"
    uid: 2067d1ed-d93f-4606-ac19-c3b331a00d5c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4m4wn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:26:57Z"
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.206637ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:08:57Z"
    - latency: 2.198091ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 2.367987ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 2.63482ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 2.237939ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 2.09519ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:03:57Z"
    - latency: 2.386857ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:57Z"
    - latency: 2.258736ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:57Z"
    - latency: 2.221672ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:57Z"
    - latency: 2.098094ms
      message: 'network-check-target-ip-10-0-136-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:19:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-105-to-network-check-target-ip-10-0-139-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-105.ec2.internal
      uid: afb07787-6716-499c-b776-760f27c58867
    resourceVersion: "68874"
    uid: 2d04842d-92b7-45c8-b07c-e9aaf82b3ae8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4m4wn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:26:57Z"
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.723µs
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:08:57Z"
    - latency: 966.839µs
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 957.702µs
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 875.295µs
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 1.326249ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 1.044329ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:03:57Z"
    - latency: 904.632µs
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:57Z"
    - latency: 1.494901ms
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:57Z"
    - latency: 943.685µs
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:57Z"
    - latency: 776.096µs
      message: 'network-check-target-ip-10-0-139-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:19:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-105-to-network-check-target-ip-10-0-141-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-105.ec2.internal
      uid: afb07787-6716-499c-b776-760f27c58867
    resourceVersion: "68876"
    uid: 86599cdd-0250-4cd2-b875-1e6328f1a72a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4m4wn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:26:57Z"
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.008323ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:08:57Z"
    - latency: 1.79078ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 2.160687ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 1.859233ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 1.955347ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 1.982607ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:03:57Z"
    - latency: 1.786777ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:57Z"
    - latency: 1.923982ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:57Z"
    - latency: 2.286181ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:57Z"
    - latency: 1.847351ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:19:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-105.ec2.internal
      uid: afb07787-6716-499c-b776-760f27c58867
    resourceVersion: "67905"
    uid: b435bc4b-ceb0-420f-a69b-3f2b77e2efe1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-4m4wn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:25:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.319µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 2.452023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:07:57Z"
    - latency: 862.572µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 1.904716ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:06:57Z"
    - latency: 996.832µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 2.128729ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:05:57Z"
    - latency: 948.523µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 1.671384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:04:57Z"
    - latency: 1.215516ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:03:57Z"
    - latency: 2.111373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:03:57Z"
kind: List
metadata:
  resourceVersion: ""