apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:18:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: 8079d5d0-0d30-4826-abbf-41348d77414d
    resourceVersion: "53756"
    uid: 500c1464-7b09-4fa3-a983-e0a2d7d00d87
  spec:
    sourcePod: network-check-source-685456655f-jkz86
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:25:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.664996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 1.010468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 869.541µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:44:52Z"
    - latency: 1.002792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:43:52Z"
    - latency: 1.275728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:42:52Z"
    - latency: 952.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:41:52Z"
    - latency: 778.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:40:52Z"
    - latency: 1.124248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:39:52Z"
    - latency: 923.925µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:38:52Z"
    - latency: 1.188963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:18:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: 8079d5d0-0d30-4826-abbf-41348d77414d
    resourceVersion: "55334"
    uid: 3ec80177-e806-48c3-859c-4d6c53bded58
  spec:
    sourcePod: network-check-source-685456655f-jkz86
    targetEndpoint: a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:24:52Z"
      message: 'load-balancer-api-external: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.500054ms
      message: 'load-balancer-api-external: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:48:52Z"
    - latency: 10.604428ms
      message: 'load-balancer-api-external: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:48:52Z"
    - latency: 5.613945ms
      message: 'load-balancer-api-external: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:47:52Z"
    - latency: 10.65875ms
      message: 'load-balancer-api-external: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:47:52Z"
    - latency: 4.27075ms
      message: 'load-balancer-api-external: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 7.026201ms
      message: 'load-balancer-api-external: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 4.482371ms
      message: 'load-balancer-api-external: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 8.478663ms
      message: 'load-balancer-api-external: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 5.499472ms
      message: 'load-balancer-api-external: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:44:52Z"
    - latency: 6.518378ms
      message: 'load-balancer-api-external: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:44:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:18:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: 8079d5d0-0d30-4826-abbf-41348d77414d
    resourceVersion: "55335"
    uid: 0008aff7-725c-42e8-9e90-1e6a4d4bc037
  spec:
    sourcePod: network-check-source-685456655f-jkz86
    targetEndpoint: a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:24:52Z"
      message: 'load-balancer-api-internal: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.671622ms
      message: 'load-balancer-api-internal: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:48:52Z"
    - latency: 10.65397ms
      message: 'load-balancer-api-internal: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:48:52Z"
    - latency: 5.570035ms
      message: 'load-balancer-api-internal: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:47:52Z"
    - latency: 10.692382ms
      message: 'load-balancer-api-internal: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:47:52Z"
    - latency: 4.212233ms
      message: 'load-balancer-api-internal: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 7.080049ms
      message: 'load-balancer-api-internal: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 4.648375ms
      message: 'load-balancer-api-internal: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 8.437206ms
      message: 'load-balancer-api-internal: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 4.815687ms
      message: 'load-balancer-api-internal: tcp connection to a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:44:52Z"
    - latency: 6.566124ms
      message: 'load-balancer-api-internal: resolved host name a8a94af3cd20a44a08aea4f3c7e7120c-1b98d7c6f1b49ab4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:44:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:18:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-ip-10-0-134-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: 8079d5d0-0d30-4826-abbf-41348d77414d
    resourceVersion: "53754"
    uid: b021cda8-12ab-4e86-8e65-77b00f01cc8b
  spec:
    sourcePod: network-check-source-685456655f-jkz86
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:25:52Z"
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.343421ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 3.033768ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 2.061558ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:44:52Z"
    - latency: 2.111963ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:43:52Z"
    - latency: 2.473605ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:42:52Z"
    - latency: 2.584874ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:41:52Z"
    - latency: 2.269568ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:40:52Z"
    - latency: 2.506202ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:39:52Z"
    - latency: 2.450831ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:38:52Z"
    - latency: 2.421806ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:18:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-ip-10-0-141-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: 8079d5d0-0d30-4826-abbf-41348d77414d
    resourceVersion: "53755"
    uid: b741f38c-6cae-4e51-a7d2-973a772fc2b7
  spec:
    sourcePod: network-check-source-685456655f-jkz86
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:25:52Z"
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.155731ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 2.795318ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 2.069768ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:44:52Z"
    - latency: 2.013949ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:43:52Z"
    - latency: 2.014688ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:42:52Z"
    - latency: 2.317126ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:41:52Z"
    - latency: 2.082652ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:40:52Z"
    - latency: 2.192608ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:39:52Z"
    - latency: 2.072796ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:38:52Z"
    - latency: 2.242873ms
      message: 'network-check-target-ip-10-0-141-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:18:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-ip-10-0-142-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: 8079d5d0-0d30-4826-abbf-41348d77414d
    resourceVersion: "53753"
    uid: 5137566c-c4ab-4a1f-9ab2-272481e45e5e
  spec:
    sourcePod: network-check-source-685456655f-jkz86
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:25:52Z"
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.852µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 1.547019ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 1.168707ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:44:52Z"
    - latency: 909.414µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:43:52Z"
    - latency: 1.5684ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:42:52Z"
    - latency: 1.377484ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:41:52Z"
    - latency: 774.993µs
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:40:52Z"
    - latency: 1.013337ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:39:52Z"
    - latency: 1.099681ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:38:52Z"
    - latency: 1.151241ms
      message: 'network-check-target-ip-10-0-142-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:37:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:18:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-37.ec2.internal
      uid: 8079d5d0-0d30-4826-abbf-41348d77414d
    resourceVersion: "55333"
    uid: 351b8fd2-227b-4e57-a07c-55d599422e72
  spec:
    sourcePod: network-check-source-685456655f-jkz86
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:24:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.991µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:48:52Z"
    - latency: 1.678609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:48:52Z"
    - latency: 1.202141ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:47:52Z"
    - latency: 1.793466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:47:52Z"
    - latency: 1.114992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 1.805471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:46:52Z"
    - latency: 902.317µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 2.732099ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:45:52Z"
    - latency: 1.083252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:44:52Z"
    - latency: 1.992898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:44:52Z"
kind: List
metadata:
  resourceVersion: ""