apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T13:45:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-16-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-16.ec2.internal
      uid: 3b5aeace-a46b-4869-85ec-491b2cb96e71
    resourceVersion: "19915"
    uid: 27019287-630d-4dfd-b101-063adba48259
  spec:
    sourcePod: network-check-source-cc88fdd44-z42dm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T13:52:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.857µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 911.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:05:25Z"
    - latency: 1.827203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:04:25Z"
    - latency: 909.103µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:03:25Z"
    - latency: 1.210989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:02:25Z"
    - latency: 898.207µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:01:25Z"
    - latency: 1.824561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:00:25Z"
    - latency: 1.589446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:59:25Z"
    - latency: 782.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:58:25Z"
    - latency: 973.971µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:57:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T13:45:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-16-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-16.ec2.internal
      uid: 3b5aeace-a46b-4869-85ec-491b2cb96e71
    resourceVersion: "20904"
    uid: e6187fed-3808-4d38-80e5-b7c2e619866d
  spec:
    sourcePod: network-check-source-cc88fdd44-z42dm
    targetEndpoint: a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T13:51:25Z"
      message: 'load-balancer-api-external: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.061783ms
      message: 'load-balancer-api-external: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:09:25Z"
    - latency: 10.401607ms
      message: 'load-balancer-api-external: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:09:25Z"
    - latency: 7.313716ms
      message: 'load-balancer-api-external: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:08:25Z"
    - latency: 8.376909ms
      message: 'load-balancer-api-external: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:08:25Z"
    - latency: 5.598879ms
      message: 'load-balancer-api-external: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:07:25Z"
    - latency: 8.489382ms
      message: 'load-balancer-api-external: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:07:25Z"
    - latency: 5.165457ms
      message: 'load-balancer-api-external: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 8.288382ms
      message: 'load-balancer-api-external: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 5.559834ms
      message: 'load-balancer-api-external: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:05:25Z"
    - latency: 8.517165ms
      message: 'load-balancer-api-external: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:05:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T13:45:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-16-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-16.ec2.internal
      uid: 3b5aeace-a46b-4869-85ec-491b2cb96e71
    resourceVersion: "20903"
    uid: 833051ea-0a1a-4ffd-bbc5-8c375ba3f4d7
  spec:
    sourcePod: network-check-source-cc88fdd44-z42dm
    targetEndpoint: a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T13:51:25Z"
      message: 'load-balancer-api-internal: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.12454ms
      message: 'load-balancer-api-internal: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:09:25Z"
    - latency: 10.460493ms
      message: 'load-balancer-api-internal: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:09:25Z"
    - latency: 7.311307ms
      message: 'load-balancer-api-internal: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:08:25Z"
    - latency: 8.234012ms
      message: 'load-balancer-api-internal: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:08:25Z"
    - latency: 4.936714ms
      message: 'load-balancer-api-internal: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:07:25Z"
    - latency: 8.525902ms
      message: 'load-balancer-api-internal: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:07:25Z"
    - latency: 5.16425ms
      message: 'load-balancer-api-internal: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 8.36727ms
      message: 'load-balancer-api-internal: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 5.552952ms
      message: 'load-balancer-api-internal: tcp connection to a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:05:25Z"
    - latency: 8.624567ms
      message: 'load-balancer-api-internal: resolved host name a8b3848104431413f87b0ce07c9a26cf-954488d8a8daa5c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:05:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T13:45:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-139-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-16.ec2.internal
      uid: 3b5aeace-a46b-4869-85ec-491b2cb96e71
    resourceVersion: "19914"
    uid: 45d14ec5-ca69-44e7-b4fa-670b3a0ea3bc
  spec:
    sourcePod: network-check-source-cc88fdd44-z42dm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T13:52:25Z"
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.095173ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 2.089901ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:05:25Z"
    - latency: 3.024546ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:04:25Z"
    - latency: 1.929983ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:03:25Z"
    - latency: 2.068944ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:02:25Z"
    - latency: 2.220724ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:01:25Z"
    - latency: 2.307477ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:00:25Z"
    - latency: 2.754342ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:59:25Z"
    - latency: 2.181252ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:58:25Z"
    - latency: 2.151828ms
      message: 'network-check-target-ip-10-0-139-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:57:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T13:45:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-142-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-16.ec2.internal
      uid: 3b5aeace-a46b-4869-85ec-491b2cb96e71
    resourceVersion: "19913"
    uid: fa76f25d-c4de-43f6-be67-a039ee8802e0
  spec:
    sourcePod: network-check-source-cc88fdd44-z42dm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T13:52:25Z"
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286179ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 2.298155ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:05:25Z"
    - latency: 3.020524ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:04:25Z"
    - latency: 2.176757ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:03:25Z"
    - latency: 2.350925ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:02:25Z"
    - latency: 2.297334ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:01:25Z"
    - latency: 3.102327ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:00:25Z"
    - latency: 2.573245ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:59:25Z"
    - latency: 2.386593ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:58:25Z"
    - latency: 2.111106ms
      message: 'network-check-target-ip-10-0-142-111: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:57:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T13:45:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-142-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-16.ec2.internal
      uid: 3b5aeace-a46b-4869-85ec-491b2cb96e71
    resourceVersion: "19912"
    uid: a398265a-fd33-45b7-8929-47b2b7cd670b
  spec:
    sourcePod: network-check-source-cc88fdd44-z42dm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T13:52:25Z"
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017124ms
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 867.941µs
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:05:25Z"
    - latency: 1.323783ms
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:04:25Z"
    - latency: 1.237311ms
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:03:25Z"
    - latency: 895.561µs
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:02:25Z"
    - latency: 882.155µs
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:01:25Z"
    - latency: 930.644µs
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:00:25Z"
    - latency: 1.515502ms
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:59:25Z"
    - latency: 910.779µs
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:58:25Z"
    - latency: 1.143417ms
      message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T13:57:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T13:45:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-16-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-16.ec2.internal
      uid: 3b5aeace-a46b-4869-85ec-491b2cb96e71
    resourceVersion: "20902"
    uid: e48f3899-8230-4a4d-8e55-298a73239405
  spec:
    sourcePod: network-check-source-cc88fdd44-z42dm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T13:51:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 864.935µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:09:25Z"
    - latency: 1.836948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:09:25Z"
    - latency: 832.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:08:25Z"
    - latency: 1.745181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:08:25Z"
    - latency: 993.942µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:07:25Z"
    - latency: 2.332102ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:07:25Z"
    - latency: 956.986µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 1.844654ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:06:25Z"
    - latency: 820.164µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:05:25Z"
    - latency: 1.945863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:05:25Z"
kind: List
metadata:
  resourceVersion: ""