apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:35:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-241-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-241.ec2.internal
      uid: 610ca226-f785-4d3e-bdc9-b253c7d89ce5
    resourceVersion: "62902"
    uid: 5ecaf54f-dbb9-43fd-bc98-41cd839a4a65
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghtx2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:42:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.142804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 1.377497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 1.019726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 893.471µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 1.159169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:13:21Z"
    - latency: 1.022425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:12:21Z"
    - latency: 1.088127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:11:21Z"
    - latency: 1.05725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:10:21Z"
    - latency: 1.294244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:09:21Z"
    - latency: 1.80795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:08:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:35:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-241-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-241.ec2.internal
      uid: 610ca226-f785-4d3e-bdc9-b253c7d89ce5
    resourceVersion: "62904"
    uid: 59691e87-749e-4366-8bf7-0d4e0320aa95
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghtx2
    targetEndpoint: a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:41:21Z"
      message: 'load-balancer-api-external: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.269418ms
      message: 'load-balancer-api-external: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 7.944641ms
      message: 'load-balancer-api-external: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 4.222111ms
      message: 'load-balancer-api-external: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 6.963374ms
      message: 'load-balancer-api-external: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 3.492691ms
      message: 'load-balancer-api-external: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 7.033445ms
      message: 'load-balancer-api-external: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 3.776114ms
      message: 'load-balancer-api-external: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 8.512371ms
      message: 'load-balancer-api-external: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 4.668678ms
      message: 'load-balancer-api-external: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:13:21Z"
    - latency: 8.418457ms
      message: 'load-balancer-api-external: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:13:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:35:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-241-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-241.ec2.internal
      uid: 610ca226-f785-4d3e-bdc9-b253c7d89ce5
    resourceVersion: "62903"
    uid: a84097dd-a0e2-4b56-9183-6b40620d3ce4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghtx2
    targetEndpoint: a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:41:21Z"
      message: 'load-balancer-api-internal: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.784822ms
      message: 'load-balancer-api-internal: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 7.914197ms
      message: 'load-balancer-api-internal: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 3.246395ms
      message: 'load-balancer-api-internal: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 7.023245ms
      message: 'load-balancer-api-internal: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 4.177499ms
      message: 'load-balancer-api-internal: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 6.951206ms
      message: 'load-balancer-api-internal: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 3.789424ms
      message: 'load-balancer-api-internal: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 8.606188ms
      message: 'load-balancer-api-internal: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 4.034265ms
      message: 'load-balancer-api-internal: tcp connection to a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:13:21Z"
    - latency: 8.271194ms
      message: 'load-balancer-api-internal: resolved host name a9f4d762250e1463087cdfc18936d27d-8dcecaadcb520fed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:13:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:35:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-241-to-network-check-target-ip-10-0-130-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-241.ec2.internal
      uid: 610ca226-f785-4d3e-bdc9-b253c7d89ce5
    resourceVersion: "62898"
    uid: 38bf8de3-dcb1-4d5a-93c9-0a3b8d5eda7e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghtx2
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:42:21Z"
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.806897ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 1.794192ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 1.834337ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 1.799999ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 2.048591ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:13:21Z"
    - latency: 1.998713ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:12:21Z"
    - latency: 2.060841ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:11:21Z"
    - latency: 1.924297ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:10:21Z"
    - latency: 2.740514ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:09:21Z"
    - latency: 2.156691ms
      message: 'network-check-target-ip-10-0-130-112: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:08:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:35:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-241-to-network-check-target-ip-10-0-130-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-241.ec2.internal
      uid: 610ca226-f785-4d3e-bdc9-b253c7d89ce5
    resourceVersion: "62900"
    uid: 350864bf-2cec-4014-a925-3d74567dfca7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghtx2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:42:21Z"
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.331462ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 1.990708ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 2.27071ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 2.184452ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 2.25553ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:13:21Z"
    - latency: 2.110237ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:12:21Z"
    - latency: 2.2187ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:11:21Z"
    - latency: 2.152203ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:10:21Z"
    - latency: 2.326166ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:09:21Z"
    - latency: 2.265863ms
      message: 'network-check-target-ip-10-0-130-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:08:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:35:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-241-to-network-check-target-ip-10-0-131-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-241.ec2.internal
      uid: 610ca226-f785-4d3e-bdc9-b253c7d89ce5
    resourceVersion: "62899"
    uid: 182b1665-75b4-45d7-aa9d-e6e6553731b5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghtx2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:42:21Z"
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.776µs
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 1.262768ms
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 1.129009ms
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 671.224µs
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 921.023µs
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:13:21Z"
    - latency: 787.822µs
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:12:21Z"
    - latency: 893.526µs
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:11:21Z"
    - latency: 973.397µs
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:10:21Z"
    - latency: 936.39µs
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:09:21Z"
    - latency: 1.679541ms
      message: 'network-check-target-ip-10-0-131-241: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:08:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T14:35:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-241-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-241.ec2.internal
      uid: 610ca226-f785-4d3e-bdc9-b253c7d89ce5
    resourceVersion: "62901"
    uid: d3eb4b25-9b26-47d4-93eb-7ee0616dc7a8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghtx2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T14:41:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.161777ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 1.725637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:17:21Z"
    - latency: 1.281828ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 1.696809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:16:21Z"
    - latency: 1.017785ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 1.744028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:15:21Z"
    - latency: 780.493µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 2.444809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:14:21Z"
    - latency: 1.014683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T15:13:21Z"
    - latency: 1.745362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T15:13:21Z"
kind: List
metadata:
  resourceVersion: ""