apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 9f2d35c0-373e-4ccb-819f-21b15cf56d93
    resourceVersion: "209423"
    uid: fd5edea1-0233-4d0f-b02b-8f8694476ca9
  spec:
    sourcePod: network-check-source-6f78d59f99-nkjt5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015894ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:23:59Z"
    - latency: 1.431946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:22:59Z"
    - latency: 1.050959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 9.018823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 1.577806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 1.103122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 1.67381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:17:59Z"
    - latency: 10.390355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:16:59Z"
    - latency: 1.284994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:15:59Z"
    - latency: 1.446986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 9f2d35c0-373e-4ccb-819f-21b15cf56d93
    resourceVersion: "207939"
    uid: 26e6c540-1138-44d3-b32a-4a5c6538498e
  spec:
    sourcePod: network-check-source-6f78d59f99-nkjt5
    targetEndpoint: a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:51:59Z"
      message: 'load-balancer-api-external: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.002568ms
      message: 'load-balancer-api-external: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 7.024903ms
      message: 'load-balancer-api-external: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 19.272228ms
      message: 'load-balancer-api-external: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 58.279342ms
      message: 'load-balancer-api-external: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 17.366615ms
      message: 'load-balancer-api-external: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 6.889052ms
      message: 'load-balancer-api-external: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 22.560868ms
      message: 'load-balancer-api-external: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 7.370025ms
      message: 'load-balancer-api-external: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 18.655165ms
      message: 'load-balancer-api-external: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:17:59Z"
    - latency: 6.166581ms
      message: 'load-balancer-api-external: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:17:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 9f2d35c0-373e-4ccb-819f-21b15cf56d93
    resourceVersion: "209424"
    uid: afdcb2c1-273f-425b-a93b-3eecb1c23656
  spec:
    sourcePod: network-check-source-6f78d59f99-nkjt5
    targetEndpoint: a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:51:59Z"
      message: 'load-balancer-api-internal: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.943327ms
      message: 'load-balancer-api-internal: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:23:59Z"
    - latency: 5.732313ms
      message: 'load-balancer-api-internal: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:23:59Z"
    - latency: 17.090464ms
      message: 'load-balancer-api-internal: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:22:59Z"
    - latency: 7.768114ms
      message: 'load-balancer-api-internal: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:22:59Z"
    - latency: 18.008864ms
      message: 'load-balancer-api-internal: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 6.976674ms
      message: 'load-balancer-api-internal: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 18.975028ms
      message: 'load-balancer-api-internal: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 53.283726ms
      message: 'load-balancer-api-internal: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 28.470686ms
      message: 'load-balancer-api-internal: tcp connection to a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 6.977772ms
      message: 'load-balancer-api-internal: resolved host name a08c1cf70531f4f9bb3d019389bdf05e-9096eb08df704de8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:19:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-131-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 9f2d35c0-373e-4ccb-819f-21b15cf56d93
    resourceVersion: "209421"
    uid: ecd6969c-5014-467b-bd4a-bab2dab7d68b
  spec:
    sourcePod: network-check-source-6f78d59f99-nkjt5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:59Z"
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.477179ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:23:59Z"
    - latency: 2.691901ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:22:59Z"
    - latency: 2.474723ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 5.778183ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 2.36382ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 2.640525ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 2.384849ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:17:59Z"
    - latency: 8.989067ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:16:59Z"
    - latency: 2.707601ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:15:59Z"
    - latency: 2.88535ms
      message: 'network-check-target-ip-10-0-131-98: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-139-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 9f2d35c0-373e-4ccb-819f-21b15cf56d93
    resourceVersion: "209420"
    uid: 300d8061-c026-4948-83e0-8bab221ca4b2
  spec:
    sourcePod: network-check-source-6f78d59f99-nkjt5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:59Z"
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.969µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:23:59Z"
    - latency: 759.11µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:22:59Z"
    - latency: 1.076417ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 13.873622ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 921.394µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 1.054154ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 912.54µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:17:59Z"
    - latency: 8.954143ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:16:59Z"
    - latency: 995.756µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:15:59Z"
    - latency: 1.601938ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-140-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 9f2d35c0-373e-4ccb-819f-21b15cf56d93
    resourceVersion: "209422"
    uid: c00da495-60a0-4dd4-9092-68422ce545a0
  spec:
    sourcePod: network-check-source-6f78d59f99-nkjt5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:59Z"
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.461233ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:23:59Z"
    - latency: 2.092294ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:22:59Z"
    - latency: 2.84961ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 13.647472ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 2.690159ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 2.322788ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 2.233801ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:17:59Z"
    - latency: 8.902111ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:16:59Z"
    - latency: 2.051624ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:15:59Z"
    - latency: 2.582299ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:14:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.ec2.internal
      uid: 9f2d35c0-373e-4ccb-819f-21b15cf56d93
    resourceVersion: "207938"
    uid: 0fb0de77-7b26-4d9d-a410-a7eedd9351eb
  spec:
    sourcePod: network-check-source-6f78d59f99-nkjt5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:51:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.318476ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 1.843938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:21:59Z"
    - latency: 4.945429ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 19.663833ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:20:59Z"
    - latency: 1.010093ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 1.847325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:19:59Z"
    - latency: 1.000125ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 1.904535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:18:59Z"
    - latency: 1.076419ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:17:59Z"
    - latency: 1.841281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T15:17:59Z"
kind: List
metadata:
  resourceVersion: ""