apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:47:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.ec2.internal
      uid: 13c4c66b-41fb-48f1-bd0a-0e309cba9e8e
    resourceVersion: "21719"
    uid: 7522acc1-2348-4005-8c25-7244d9265ee2
  spec:
    sourcePod: network-check-source-6f8b768455-575lc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:54:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.694295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:01:35Z"
    - latency: 980.514µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:00:35Z"
    - latency: 1.243677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 904.32µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 1.525103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 835.151µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 1.718945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:55:35Z"
    - latency: 1.148166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:54:35Z"
    - latency: 1.491037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:53:35Z"
    - latency: 934.55µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:47:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.ec2.internal
      uid: 13c4c66b-41fb-48f1-bd0a-0e309cba9e8e
    resourceVersion: "20698"
    uid: 6fb81688-d0f1-41c3-9e6e-ffa5737b2148
  spec:
    sourcePod: network-check-source-6f8b768455-575lc
    targetEndpoint: a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:53:35Z"
      message: 'load-balancer-api-external: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.2198ms
      message: 'load-balancer-api-external: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 8.140499ms
      message: 'load-balancer-api-external: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 4.724024ms
      message: 'load-balancer-api-external: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 8.437465ms
      message: 'load-balancer-api-external: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 5.168744ms
      message: 'load-balancer-api-external: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 8.011839ms
      message: 'load-balancer-api-external: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 5.20764ms
      message: 'load-balancer-api-external: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 8.747951ms
      message: 'load-balancer-api-external: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 4.83355ms
      message: 'load-balancer-api-external: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:55:35Z"
    - latency: 8.479198ms
      message: 'load-balancer-api-external: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:55:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:47:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.ec2.internal
      uid: 13c4c66b-41fb-48f1-bd0a-0e309cba9e8e
    resourceVersion: "20697"
    uid: 29b5ba78-cf66-488a-8b50-6cb4db74e75a
  spec:
    sourcePod: network-check-source-6f8b768455-575lc
    targetEndpoint: a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:53:35Z"
      message: 'load-balancer-api-internal: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.857885ms
      message: 'load-balancer-api-internal: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 8.242743ms
      message: 'load-balancer-api-internal: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 4.864617ms
      message: 'load-balancer-api-internal: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 8.410207ms
      message: 'load-balancer-api-internal: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 5.161303ms
      message: 'load-balancer-api-internal: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 7.946453ms
      message: 'load-balancer-api-internal: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 5.178571ms
      message: 'load-balancer-api-internal: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 8.826962ms
      message: 'load-balancer-api-internal: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 4.783991ms
      message: 'load-balancer-api-internal: tcp connection to a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:55:35Z"
    - latency: 8.460827ms
      message: 'load-balancer-api-internal: resolved host name a92ef190805bb447daab4f3753ddfb60-fc725f57f88482b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:55:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:47:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-ip-10-0-129-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.ec2.internal
      uid: 13c4c66b-41fb-48f1-bd0a-0e309cba9e8e
    resourceVersion: "21716"
    uid: 4b518b14-57cf-46bf-8430-1b1d32543688
  spec:
    sourcePod: network-check-source-6f8b768455-575lc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:54:35Z"
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 800.918µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:01:35Z"
    - latency: 992.917µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:00:35Z"
    - latency: 846.795µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 749.43µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 744.666µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 1.001011ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 814.757µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:55:35Z"
    - latency: 975.231µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:54:35Z"
    - latency: 752.571µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:53:35Z"
    - latency: 838.098µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:47:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-ip-10-0-130-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.ec2.internal
      uid: 13c4c66b-41fb-48f1-bd0a-0e309cba9e8e
    resourceVersion: "21718"
    uid: 524abba5-3b16-4200-bef0-17f9047b12e0
  spec:
    sourcePod: network-check-source-6f8b768455-575lc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:54:35Z"
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.297204ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:01:35Z"
    - latency: 2.438536ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:00:35Z"
    - latency: 2.317394ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 2.195758ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 2.663475ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 1.971291ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 2.905557ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:55:35Z"
    - latency: 2.320591ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:54:35Z"
    - latency: 2.126319ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:53:35Z"
    - latency: 2.200859ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:47:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-ip-10-0-134-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.ec2.internal
      uid: 13c4c66b-41fb-48f1-bd0a-0e309cba9e8e
    resourceVersion: "21717"
    uid: a01ca674-21ec-488d-b109-0d67dab168bb
  spec:
    sourcePod: network-check-source-6f8b768455-575lc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:54:35Z"
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.206802ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:01:35Z"
    - latency: 2.288377ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:00:35Z"
    - latency: 2.260204ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 2.020765ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 2.136782ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 2.466959ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 2.187099ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:55:35Z"
    - latency: 2.33821ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:54:35Z"
    - latency: 2.476201ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:53:35Z"
    - latency: 2.017085ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T17:47:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.ec2.internal
      uid: 13c4c66b-41fb-48f1-bd0a-0e309cba9e8e
    resourceVersion: "20696"
    uid: 131d1e10-b486-4ccc-b5e5-595775f4d4b1
  spec:
    sourcePod: network-check-source-6f8b768455-575lc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T17:53:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.772µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 1.615564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:59:35Z"
    - latency: 1.181055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 1.650255ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:58:35Z"
    - latency: 1.017556ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 2.021052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:57:35Z"
    - latency: 1.006453ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 1.634959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:56:35Z"
    - latency: 861.458µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:55:35Z"
    - latency: 2.22512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:55:35Z"
kind: List
metadata:
  resourceVersion: ""