apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-147-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-147.ec2.internal
      uid: e2a748d9-339c-483b-9883-34690901638d
    resourceVersion: "66636"
    uid: 7b1389c8-9355-41ff-8ddc-b37ce69ed582
  spec:
    sourcePod: network-check-source-6f78d59f99-xsw6d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:59:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.283973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:27:53Z"
    - latency: 853.612µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:26:53Z"
    - latency: 1.254949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:25:53Z"
    - latency: 1.071444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:24:53Z"
    - latency: 1.203938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:23:53Z"
    - latency: 1.147972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 1.122694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 1.406131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 986.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 1.028004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:18:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-147-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-147.ec2.internal
      uid: e2a748d9-339c-483b-9883-34690901638d
    resourceVersion: "62151"
    uid: 53ef1c19-2490-4a5e-b190-219326dd0f01
  spec:
    sourcePod: network-check-source-6f78d59f99-xsw6d
    targetEndpoint: a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:58:53Z"
      message: 'load-balancer-api-external: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.78555ms
      message: 'load-balancer-api-external: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 6.90364ms
      message: 'load-balancer-api-external: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 16.13038ms
      message: 'load-balancer-api-external: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 9.550342ms
      message: 'load-balancer-api-external: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 13.747563ms
      message: 'load-balancer-api-external: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 6.559905ms
      message: 'load-balancer-api-external: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 21.236398ms
      message: 'load-balancer-api-external: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 6.242643ms
      message: 'load-balancer-api-external: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 12.97407ms
      message: 'load-balancer-api-external: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:18:53Z"
    - latency: 19.75435ms
      message: 'load-balancer-api-external: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:18:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-147-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-147.ec2.internal
      uid: e2a748d9-339c-483b-9883-34690901638d
    resourceVersion: "62152"
    uid: e984e27d-68e4-429f-902b-359966578314
  spec:
    sourcePod: network-check-source-6f78d59f99-xsw6d
    targetEndpoint: a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:58:53Z"
      message: 'load-balancer-api-internal: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.269589ms
      message: 'load-balancer-api-internal: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 6.84659ms
      message: 'load-balancer-api-internal: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 16.139135ms
      message: 'load-balancer-api-internal: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 9.569803ms
      message: 'load-balancer-api-internal: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 17.326695ms
      message: 'load-balancer-api-internal: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 6.490743ms
      message: 'load-balancer-api-internal: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 15.393009ms
      message: 'load-balancer-api-internal: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 6.094946ms
      message: 'load-balancer-api-internal: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 16.334317ms
      message: 'load-balancer-api-internal: tcp connection to a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:18:53Z"
    - latency: 19.787907ms
      message: 'load-balancer-api-internal: resolved host name a880dd625d1e94eb5bf2e72c1407ac95-0bc09fb3b8f4e1ac.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:18:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-147-to-network-check-target-ip-10-0-130-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-147.ec2.internal
      uid: e2a748d9-339c-483b-9883-34690901638d
    resourceVersion: "66634"
    uid: 890319cb-4a38-4168-9b67-39ede7630ece
  spec:
    sourcePod: network-check-source-6f78d59f99-xsw6d
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:59:53Z"
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.288481ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:27:53Z"
    - latency: 1.904751ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:26:53Z"
    - latency: 1.83048ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:25:53Z"
    - latency: 2.185082ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:24:53Z"
    - latency: 2.378452ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:23:53Z"
    - latency: 2.69063ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 2.098409ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 2.338353ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 2.644355ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 2.338799ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:18:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:52:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-147-to-network-check-target-ip-10-0-137-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-147.ec2.internal
      uid: e2a748d9-339c-483b-9883-34690901638d
    resourceVersion: "66688"
    uid: f52aeb03-f10c-4a65-9f04-b61f08061365
  spec:
    sourcePod: network-check-source-6f78d59f99-xsw6d
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:59:58Z"
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.229962ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:27:58Z"
    - latency: 1.006711ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:26:58Z"
    - latency: 1.753397ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:25:58Z"
    - latency: 1.035498ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:24:58Z"
    - latency: 3.419116ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:23:58Z"
    - latency: 2.072279ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:22:58Z"
    - latency: 3.103055ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:21:58Z"
    - latency: 2.224662ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:20:58Z"
    - latency: 2.408935ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:19:58Z"
    - latency: 1.903464ms
      message: 'network-check-target-ip-10-0-137-21: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:18:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-147-to-network-check-target-ip-10-0-141-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-147.ec2.internal
      uid: e2a748d9-339c-483b-9883-34690901638d
    resourceVersion: "66635"
    uid: 5e9e6337-f476-4acd-97d7-b8a0e7e9dd96
  spec:
    sourcePod: network-check-source-6f78d59f99-xsw6d
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:59:53Z"
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.756892ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:27:53Z"
    - latency: 911.777µs
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:26:53Z"
    - latency: 1.394955ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:25:53Z"
    - latency: 1.083753ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:24:53Z"
    - latency: 1.440881ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:23:53Z"
    - latency: 851.842µs
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 1.430959ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 1.348261ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 1.740296ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 1.448468ms
      message: 'network-check-target-ip-10-0-141-147: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:18:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:52:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-147-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-147.ec2.internal
      uid: e2a748d9-339c-483b-9883-34690901638d
    resourceVersion: "62146"
    uid: b2044e8a-fd35-4a82-84ad-2b76ba2931b5
  spec:
    sourcePod: network-check-source-6f78d59f99-xsw6d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:58:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.314409ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 1.688859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:22:53Z"
    - latency: 877.434µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 1.957859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:21:53Z"
    - latency: 1.000707ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 1.728536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:20:53Z"
    - latency: 1.100092ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 1.719047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:19:53Z"
    - latency: 854.242µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:18:53Z"
    - latency: 1.499144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:18:53Z"
kind: List
metadata:
  resourceVersion: ""