apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T21:09:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-253-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-253.ec2.internal
      uid: 4b56b675-bfbd-48e6-9092-1e6388b03815
    resourceVersion: "64502"
    uid: dfbdf9bc-faf8-47f4-8907-fa0a3a7b152e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vm2s6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T21:16:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 843.032µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 954.55µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 781.272µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 1.046107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 940.312µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:47:12Z"
    - latency: 997.155µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:46:12Z"
    - latency: 1.276983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:45:12Z"
    - latency: 984.201µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:44:12Z"
    - latency: 794.464µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:43:12Z"
    - latency: 1.875516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:42:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T21:09:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-253-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-253.ec2.internal
      uid: 4b56b675-bfbd-48e6-9092-1e6388b03815
    resourceVersion: "64503"
    uid: e9f5ac02-c625-4731-ac9a-b27f0f6a1907
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vm2s6
    targetEndpoint: aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T21:15:12Z"
      message: 'load-balancer-api-external: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.345206ms
      message: 'load-balancer-api-external: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 9.149664ms
      message: 'load-balancer-api-external: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 3.927458ms
      message: 'load-balancer-api-external: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 7.147197ms
      message: 'load-balancer-api-external: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 4.955374ms
      message: 'load-balancer-api-external: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 7.071574ms
      message: 'load-balancer-api-external: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 3.989078ms
      message: 'load-balancer-api-external: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 7.102037ms
      message: 'load-balancer-api-external: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 5.771505ms
      message: 'load-balancer-api-external: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:47:12Z"
    - latency: 7.371641ms
      message: 'load-balancer-api-external: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:47:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T21:09:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-253-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-253.ec2.internal
      uid: 4b56b675-bfbd-48e6-9092-1e6388b03815
    resourceVersion: "64504"
    uid: 1bcb7175-f813-438b-bb1d-dcb3199d0797
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vm2s6
    targetEndpoint: aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T21:15:12Z"
      message: 'load-balancer-api-internal: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.279075ms
      message: 'load-balancer-api-internal: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 9.193313ms
      message: 'load-balancer-api-internal: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 3.974808ms
      message: 'load-balancer-api-internal: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 7.06815ms
      message: 'load-balancer-api-internal: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 4.90632ms
      message: 'load-balancer-api-internal: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 7.093776ms
      message: 'load-balancer-api-internal: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 3.157168ms
      message: 'load-balancer-api-internal: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 6.984541ms
      message: 'load-balancer-api-internal: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 5.7994ms
      message: 'load-balancer-api-internal: tcp connection to aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:47:12Z"
    - latency: 7.363778ms
      message: 'load-balancer-api-internal: resolved host name aedee9c5050474825a76a3d860dd8a9b-d785be9824ad11a4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:47:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T21:09:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-253-to-network-check-target-ip-10-0-128-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-253.ec2.internal
      uid: 4b56b675-bfbd-48e6-9092-1e6388b03815
    resourceVersion: "64498"
    uid: e992ac7b-76a3-4f6b-b0f0-9e92a96c0edf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vm2s6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T21:16:12Z"
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.002793ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 1.547279ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 1.237466ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 908.236µs
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 862.544µs
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:47:12Z"
    - latency: 821.661µs
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:46:12Z"
    - latency: 1.004949ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:45:12Z"
    - latency: 876.419µs
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:44:12Z"
    - latency: 1.392642ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:43:12Z"
    - latency: 1.099642ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:42:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T21:09:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-253-to-network-check-target-ip-10-0-136-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-253.ec2.internal
      uid: 4b56b675-bfbd-48e6-9092-1e6388b03815
    resourceVersion: "64499"
    uid: b31e2536-c793-47ba-a5be-815d98091792
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vm2s6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T21:16:12Z"
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.123448ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 2.456375ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 2.18192ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 2.304687ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 2.511973ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:47:12Z"
    - latency: 1.912613ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:46:12Z"
    - latency: 2.459694ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:45:12Z"
    - latency: 2.242872ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:44:12Z"
    - latency: 2.055254ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:43:12Z"
    - latency: 1.98973ms
      message: 'network-check-target-ip-10-0-136-242: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:42:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T21:09:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-253-to-network-check-target-ip-10-0-136-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-253.ec2.internal
      uid: 4b56b675-bfbd-48e6-9092-1e6388b03815
    resourceVersion: "64500"
    uid: 6a2c9648-5bc0-4a32-a8f3-7ffa7d7569b3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vm2s6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T21:16:12Z"
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.035597ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 1.958693ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 1.763328ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 2.047356ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 2.634272ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:47:12Z"
    - latency: 1.936744ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:46:12Z"
    - latency: 2.086604ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:45:12Z"
    - latency: 2.183302ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:44:12Z"
    - latency: 1.911113ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:43:12Z"
    - latency: 1.853259ms
      message: 'network-check-target-ip-10-0-136-32: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:42:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T21:09:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-253-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-253.ec2.internal
      uid: 4b56b675-bfbd-48e6-9092-1e6388b03815
    resourceVersion: "64501"
    uid: d3417098-3b5a-436a-b622-032fdecb04af
  spec:
    sourcePod: network-check-source-7bc5b6bf85-vm2s6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T21:15:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.399µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 1.865002ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:51:12Z"
    - latency: 915.264µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 1.603261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:50:12Z"
    - latency: 925.68µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 1.689024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:49:12Z"
    - latency: 983.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 1.825902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:48:12Z"
    - latency: 886.41µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T21:47:12Z"
    - latency: 2.585816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T21:47:12Z"
kind: List
metadata:
  resourceVersion: ""