apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:28:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-83-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-83.ec2.internal
      uid: 177a1cd1-8a82-42ae-912a-5f74329abc05
    resourceVersion: "68203"
    uid: 10938d4a-109b-41e8-89ec-b49ad0cd8b2c
  spec:
    sourcePod: network-check-source-6f8b768455-ptlrg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:35:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.070595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:03:16Z"
    - latency: 1.227806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:02:16Z"
    - latency: 1.274223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:01:16Z"
    - latency: 1.456662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:00:16Z"
    - latency: 1.037625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:59:16Z"
    - latency: 1.199353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 1.272315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 1.0339ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 954.982µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 1.231176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:54:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:28:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-83-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-83.ec2.internal
      uid: 177a1cd1-8a82-42ae-912a-5f74329abc05
    resourceVersion: "63688"
    uid: 28300880-70a2-47bb-bcfc-bcda7ad7beb3
  spec:
    sourcePod: network-check-source-6f8b768455-ptlrg
    targetEndpoint: a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:34:16Z"
      message: 'load-balancer-api-external: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.33408ms
      message: 'load-balancer-api-external: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 8.287516ms
      message: 'load-balancer-api-external: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 3.974368ms
      message: 'load-balancer-api-external: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 8.470089ms
      message: 'load-balancer-api-external: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 4.135882ms
      message: 'load-balancer-api-external: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 7.364407ms
      message: 'load-balancer-api-external: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 4.475459ms
      message: 'load-balancer-api-external: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 9.538957ms
      message: 'load-balancer-api-external: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 4.23559ms
      message: 'load-balancer-api-external: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:54:16Z"
    - latency: 10.096557ms
      message: 'load-balancer-api-external: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:54:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:28:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-83-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-83.ec2.internal
      uid: 177a1cd1-8a82-42ae-912a-5f74329abc05
    resourceVersion: "63689"
    uid: f59539e9-c7ee-4a62-86c1-640ec6f4009e
  spec:
    sourcePod: network-check-source-6f8b768455-ptlrg
    targetEndpoint: a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:34:16Z"
      message: 'load-balancer-api-internal: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.650116ms
      message: 'load-balancer-api-internal: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 8.099968ms
      message: 'load-balancer-api-internal: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 4.627169ms
      message: 'load-balancer-api-internal: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 8.369442ms
      message: 'load-balancer-api-internal: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 4.124869ms
      message: 'load-balancer-api-internal: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 7.332244ms
      message: 'load-balancer-api-internal: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 4.238337ms
      message: 'load-balancer-api-internal: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 9.461938ms
      message: 'load-balancer-api-internal: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 4.276307ms
      message: 'load-balancer-api-internal: tcp connection to a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:54:16Z"
    - latency: 10.161104ms
      message: 'load-balancer-api-internal: resolved host name a6e6e8f5674f844c39662e0811aa6d83-8c79d986880fb10f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:54:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:28:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-83-to-network-check-target-ip-10-0-130-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-83.ec2.internal
      uid: 177a1cd1-8a82-42ae-912a-5f74329abc05
    resourceVersion: "68201"
    uid: ac81fb88-8d62-4038-af50-9c87bc457ede
  spec:
    sourcePod: network-check-source-6f8b768455-ptlrg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:35:16Z"
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.178019ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:03:16Z"
    - latency: 2.372292ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:02:16Z"
    - latency: 2.133378ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:01:16Z"
    - latency: 2.204009ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:00:16Z"
    - latency: 2.472701ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:59:16Z"
    - latency: 2.362037ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 2.253003ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 2.248925ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 2.043537ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 2.365384ms
      message: 'network-check-target-ip-10-0-130-87: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:54:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:28:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-83-to-network-check-target-ip-10-0-136-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-83.ec2.internal
      uid: 177a1cd1-8a82-42ae-912a-5f74329abc05
    resourceVersion: "68199"
    uid: 7ffbccce-ad75-4c4b-9972-d1861e459571
  spec:
    sourcePod: network-check-source-6f8b768455-ptlrg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:35:16Z"
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.954345ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:03:16Z"
    - latency: 2.294334ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:02:16Z"
    - latency: 2.139353ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:01:16Z"
    - latency: 2.184853ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:00:16Z"
    - latency: 2.318784ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:59:16Z"
    - latency: 2.050778ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 1.897664ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 2.16522ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 2.123369ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 2.321116ms
      message: 'network-check-target-ip-10-0-136-54: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:54:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:28:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-83-to-network-check-target-ip-10-0-138-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-83.ec2.internal
      uid: 177a1cd1-8a82-42ae-912a-5f74329abc05
    resourceVersion: "68200"
    uid: fc50f92d-1b77-433e-9029-78fdec621433
  spec:
    sourcePod: network-check-source-6f8b768455-ptlrg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:35:16Z"
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.561925ms
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:03:16Z"
    - latency: 1.115112ms
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:02:16Z"
    - latency: 1.104635ms
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:01:16Z"
    - latency: 1.01283ms
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T02:00:16Z"
    - latency: 1.112293ms
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:59:16Z"
    - latency: 1.434767ms
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 981.188µs
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 997.483µs
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 1.465557ms
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 968.634µs
      message: 'network-check-target-ip-10-0-138-83: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:54:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T01:28:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-83-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-83.ec2.internal
      uid: 177a1cd1-8a82-42ae-912a-5f74329abc05
    resourceVersion: "63687"
    uid: 0dd1f1ff-d2f4-4346-95bf-16f1f14bb3ac
  spec:
    sourcePod: network-check-source-6f8b768455-ptlrg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T01:34:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.699µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 2.023983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:58:16Z"
    - latency: 975.239µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 1.674692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:57:16Z"
    - latency: 1.136533ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 2.044487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:56:16Z"
    - latency: 1.00316ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 1.963723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:55:16Z"
    - latency: 983.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T01:54:16Z"
    - latency: 1.718285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T01:54:16Z"
kind: List
metadata:
  resourceVersion: ""