apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-192-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-192.ec2.internal
      uid: b71b6e4d-3cb8-4383-964a-9acff86779b5
    resourceVersion: "52861"
    uid: 4706b9a5-8b7a-493d-bf59-e60496176b92
  spec:
    sourcePod: network-check-source-6f8b768455-sndmm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:58:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.743µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 1.128677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 1.388553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:47Z"
    - latency: 1.026746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:47Z"
    - latency: 1.203952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:47Z"
    - latency: 1.175622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:14:47Z"
    - latency: 1.171538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:13:47Z"
    - latency: 1.191634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:12:47Z"
    - latency: 816.927µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:11:47Z"
    - latency: 1.319244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-192-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-192.ec2.internal
      uid: b71b6e4d-3cb8-4383-964a-9acff86779b5
    resourceVersion: "54807"
    uid: 8b99645b-8fbb-449b-9d20-27cf76ebc9b5
  spec:
    sourcePod: network-check-source-6f8b768455-sndmm
    targetEndpoint: a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:57:47Z"
      message: 'load-balancer-api-external: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.96472ms
      message: 'load-balancer-api-external: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:21:47Z"
    - latency: 7.763091ms
      message: 'load-balancer-api-external: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:21:47Z"
    - latency: 12.560988ms
      message: 'load-balancer-api-external: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:20:47Z"
    - latency: 7.45536ms
      message: 'load-balancer-api-external: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:20:47Z"
    - latency: 6.692358ms
      message: 'load-balancer-api-external: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 7.689439ms
      message: 'load-balancer-api-external: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 5.855467ms
      message: 'load-balancer-api-external: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 7.098848ms
      message: 'load-balancer-api-external: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 4.944366ms
      message: 'load-balancer-api-external: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:47Z"
    - latency: 7.060117ms
      message: 'load-balancer-api-external: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:17:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-192-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-192.ec2.internal
      uid: b71b6e4d-3cb8-4383-964a-9acff86779b5
    resourceVersion: "54806"
    uid: d68a6572-e465-4067-bab1-b457412fa8b7
  spec:
    sourcePod: network-check-source-6f8b768455-sndmm
    targetEndpoint: a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:57:47Z"
      message: 'load-balancer-api-internal: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.964343ms
      message: 'load-balancer-api-internal: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:21:47Z"
    - latency: 7.748668ms
      message: 'load-balancer-api-internal: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:21:47Z"
    - latency: 6.175053ms
      message: 'load-balancer-api-internal: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:20:47Z"
    - latency: 7.472067ms
      message: 'load-balancer-api-internal: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:20:47Z"
    - latency: 6.654431ms
      message: 'load-balancer-api-internal: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 7.751675ms
      message: 'load-balancer-api-internal: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 5.881089ms
      message: 'load-balancer-api-internal: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 7.050978ms
      message: 'load-balancer-api-internal: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 4.421231ms
      message: 'load-balancer-api-internal: tcp connection to a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:47Z"
    - latency: 7.082789ms
      message: 'load-balancer-api-internal: resolved host name a4f61b1a8a3904e93883dcf9b37e0678-eb51436db3e7353a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:17:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-192-to-network-check-target-ip-10-0-128-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-192.ec2.internal
      uid: b71b6e4d-3cb8-4383-964a-9acff86779b5
    resourceVersion: "52860"
    uid: 90946cd8-592a-4de6-a92b-c5d0d071b98a
  spec:
    sourcePod: network-check-source-6f8b768455-sndmm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:58:47Z"
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.416656ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 2.1114ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 2.341416ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:47Z"
    - latency: 2.438934ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:47Z"
    - latency: 2.558891ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:47Z"
    - latency: 2.217645ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:14:47Z"
    - latency: 2.716426ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:13:47Z"
    - latency: 2.567564ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:12:47Z"
    - latency: 2.270304ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:11:47Z"
    - latency: 2.540428ms
      message: 'network-check-target-ip-10-0-128-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-192-to-network-check-target-ip-10-0-137-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-192.ec2.internal
      uid: b71b6e4d-3cb8-4383-964a-9acff86779b5
    resourceVersion: "52858"
    uid: 2360b2fc-98ca-4000-8ee3-df2f55275f80
  spec:
    sourcePod: network-check-source-6f8b768455-sndmm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:58:47Z"
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.088319ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 894.397µs
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 1.101598ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:47Z"
    - latency: 1.703288ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:47Z"
    - latency: 993.194µs
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:47Z"
    - latency: 1.23938ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:14:47Z"
    - latency: 1.202111ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:13:47Z"
    - latency: 1.579537ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:12:47Z"
    - latency: 911.252µs
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:11:47Z"
    - latency: 756.345µs
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:51:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-192-to-network-check-target-ip-10-0-139-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-192.ec2.internal
      uid: b71b6e4d-3cb8-4383-964a-9acff86779b5
    resourceVersion: "52859"
    uid: 1231e546-ed9b-4191-b51f-c626fd0807af
  spec:
    sourcePod: network-check-source-6f8b768455-sndmm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:58:47Z"
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.084279ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 2.111861ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 2.192517ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:47Z"
    - latency: 1.999875ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:47Z"
    - latency: 2.001873ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:47Z"
    - latency: 2.171588ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:14:47Z"
    - latency: 2.200263ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:13:47Z"
    - latency: 2.127008ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:12:47Z"
    - latency: 1.821147ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:11:47Z"
    - latency: 2.252063ms
      message: 'network-check-target-ip-10-0-139-201: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:51:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-192-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-192.ec2.internal
      uid: b71b6e4d-3cb8-4383-964a-9acff86779b5
    resourceVersion: "54805"
    uid: 9dea66a2-d76a-4c99-bb3f-7086b2a8dfbd
  spec:
    sourcePod: network-check-source-6f8b768455-sndmm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:57:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.566µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:21:47Z"
    - latency: 2.025695ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:21:47Z"
    - latency: 896.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:20:47Z"
    - latency: 1.873608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:20:47Z"
    - latency: 1.151472ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 1.763376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:19:47Z"
    - latency: 744.963µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 1.848781ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:18:47Z"
    - latency: 1.064921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:47Z"
    - latency: 1.791596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:17:47Z"
kind: List
metadata:
  resourceVersion: ""