apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:41:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.us-east-2.compute.internal
      uid: 196e96c3-f9c1-4917-8900-8329d3b3293f
    resourceVersion: "147183"
    uid: 7304c4c9-0353-4069-b412-507dda515487
  spec:
    sourcePod: network-check-source-6f78d59f99-f9vq4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:48:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020149ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 1.223107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:43:32Z"
    - latency: 1.026408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:42:32Z"
    - latency: 24.987471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:41:32Z"
    - latency: 994.433µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:40:32Z"
    - latency: 1.321133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:39:32Z"
    - latency: 842.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:38:32Z"
    - latency: 1.00635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:37:32Z"
    - latency: 1.252672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:36:32Z"
    - latency: 1.392086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:35:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:41:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.us-east-2.compute.internal
      uid: 196e96c3-f9c1-4917-8900-8329d3b3293f
    resourceVersion: "153823"
    uid: bc06c426-35a9-469d-9d39-bfd46d6fe8b3
  spec:
    sourcePod: network-check-source-6f78d59f99-f9vq4
    targetEndpoint: a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:47:32Z"
      message: 'load-balancer-api-external: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.059427ms
      message: 'load-balancer-api-external: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:47:32Z"
    - latency: 6.460199ms
      message: 'load-balancer-api-external: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:47:32Z"
    - latency: 6.6203ms
      message: 'load-balancer-api-external: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:46:32Z"
    - latency: 6.870975ms
      message: 'load-balancer-api-external: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:46:32Z"
    - latency: 4.978771ms
      message: 'load-balancer-api-external: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:45:32Z"
    - latency: 7.577677ms
      message: 'load-balancer-api-external: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:45:32Z"
    - latency: 5.779827ms
      message: 'load-balancer-api-external: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 7.103229ms
      message: 'load-balancer-api-external: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 4.980376ms
      message: 'load-balancer-api-external: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:43:32Z"
    - latency: 7.056816ms
      message: 'load-balancer-api-external: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:43:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:41:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.us-east-2.compute.internal
      uid: 196e96c3-f9c1-4917-8900-8329d3b3293f
    resourceVersion: "153822"
    uid: bf63fabe-0912-4bcc-9e02-9889e82d24b2
  spec:
    sourcePod: network-check-source-6f78d59f99-f9vq4
    targetEndpoint: a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:47:32Z"
      message: 'load-balancer-api-internal: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.051501ms
      message: 'load-balancer-api-internal: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:47:32Z"
    - latency: 6.402329ms
      message: 'load-balancer-api-internal: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:47:32Z"
    - latency: 6.568348ms
      message: 'load-balancer-api-internal: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:46:32Z"
    - latency: 6.908593ms
      message: 'load-balancer-api-internal: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:46:32Z"
    - latency: 4.994729ms
      message: 'load-balancer-api-internal: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:45:32Z"
    - latency: 7.50177ms
      message: 'load-balancer-api-internal: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:45:32Z"
    - latency: 5.753321ms
      message: 'load-balancer-api-internal: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 7.159069ms
      message: 'load-balancer-api-internal: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 5.015515ms
      message: 'load-balancer-api-internal: tcp connection to a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:43:32Z"
    - latency: 6.994815ms
      message: 'load-balancer-api-internal: resolved host name a91d3c7a683464b25952d96838b53569-82b4dc8764a7c21c.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:43:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:41:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-ip-10-0-128-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.us-east-2.compute.internal
      uid: 196e96c3-f9c1-4917-8900-8329d3b3293f
    resourceVersion: "147182"
    uid: bcd46164-27e4-4516-906d-fc2caab83eb3
  spec:
    sourcePod: network-check-source-6f78d59f99-f9vq4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:48:32Z"
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.415512ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 2.362037ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:43:32Z"
    - latency: 2.093287ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:42:32Z"
    - latency: 25.052125ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:41:32Z"
    - latency: 2.132883ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:40:32Z"
    - latency: 2.231063ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:39:32Z"
    - latency: 2.132082ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:38:32Z"
    - latency: 1.827545ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:37:32Z"
    - latency: 2.25098ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:36:32Z"
    - latency: 2.135725ms
      message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:35:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:41:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-ip-10-0-134-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.us-east-2.compute.internal
      uid: 196e96c3-f9c1-4917-8900-8329d3b3293f
    resourceVersion: "147180"
    uid: cd2c06ed-95be-4ebe-8d07-3f17321c27de
  spec:
    sourcePod: network-check-source-6f78d59f99-f9vq4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:48:32Z"
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.505663ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 1.690762ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:43:32Z"
    - latency: 1.050114ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:42:32Z"
    - latency: 26.222449ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:41:32Z"
    - latency: 1.004659ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:40:32Z"
    - latency: 3.176263ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:39:32Z"
    - latency: 1.705326ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:38:32Z"
    - latency: 1.960576ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:37:32Z"
    - latency: 1.637373ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:36:32Z"
    - latency: 1.597477ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:35:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:41:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-ip-10-0-142-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.us-east-2.compute.internal
      uid: 196e96c3-f9c1-4917-8900-8329d3b3293f
    resourceVersion: "147181"
    uid: 6d10994b-6ce7-442d-ac90-1b66c6aea27d
  spec:
    sourcePod: network-check-source-6f78d59f99-f9vq4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:48:32Z"
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.536518ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 2.823965ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:43:32Z"
    - latency: 2.640038ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:42:32Z"
    - latency: 10.589561ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:41:32Z"
    - latency: 2.423883ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:40:32Z"
    - latency: 3.192573ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:39:32Z"
    - latency: 2.795471ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:38:32Z"
    - latency: 2.26124ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:37:32Z"
    - latency: 2.43032ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:36:32Z"
    - latency: 2.311586ms
      message: 'network-check-target-ip-10-0-142-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:35:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:41:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-178.us-east-2.compute.internal
      uid: 196e96c3-f9c1-4917-8900-8329d3b3293f
    resourceVersion: "153821"
    uid: c55ab48d-1f16-4ab9-9589-1daf201fc119
  spec:
    sourcePod: network-check-source-6f78d59f99-f9vq4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:47:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.37873ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:47:32Z"
    - latency: 1.989882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:47:32Z"
    - latency: 1.035159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:46:32Z"
    - latency: 2.109514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:46:32Z"
    - latency: 850.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:45:32Z"
    - latency: 2.494203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:45:32Z"
    - latency: 871.049µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 1.861312ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:44:32Z"
    - latency: 895.309µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:43:32Z"
    - latency: 2.122104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:43:32Z"
kind: List
metadata:
  resourceVersion: ""