apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:44:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-60-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-60.us-west-2.compute.internal
      uid: 225a7db9-2dd0-4d43-b9f6-66d929e8bb92
    resourceVersion: "112461"
    uid: a3eeb1ed-9942-4ae6-bc43-a077492b9cc7
  spec:
    sourcePod: network-check-source-6f78d59f99-rmpxf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:51:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.979396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 1.150074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 1.063354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:33Z"
    - latency: 1.030085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:33Z"
    - latency: 1.323784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:33Z"
    - latency: 1.68686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:33Z"
    - latency: 1.294503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:33Z"
    - latency: 2.462973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:33Z"
    - latency: 1.133547ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:46:33Z"
    - latency: 1.383012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:45:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:44:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-60-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-60.us-west-2.compute.internal
      uid: 225a7db9-2dd0-4d43-b9f6-66d929e8bb92
    resourceVersion: "113522"
    uid: 44eba2de-04a5-495d-be56-63f3df4c5228
  spec:
    sourcePod: network-check-source-6f78d59f99-rmpxf
    targetEndpoint: a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:50:33Z"
      message: 'load-balancer-api-external: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 57.585516ms
      message: 'load-balancer-api-external: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:33Z"
    - latency: 6.62312ms
      message: 'load-balancer-api-external: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:33Z"
    - latency: 53.479202ms
      message: 'load-balancer-api-external: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:33Z"
    - latency: 6.74308ms
      message: 'load-balancer-api-external: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:33Z"
    - latency: 51.442225ms
      message: 'load-balancer-api-external: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 7.248734ms
      message: 'load-balancer-api-external: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 50.874665ms
      message: 'load-balancer-api-external: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 6.767791ms
      message: 'load-balancer-api-external: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 50.85962ms
      message: 'load-balancer-api-external: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:33Z"
    - latency: 11.678592ms
      message: 'load-balancer-api-external: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:52:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:44:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-60-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-60.us-west-2.compute.internal
      uid: 225a7db9-2dd0-4d43-b9f6-66d929e8bb92
    resourceVersion: "113523"
    uid: be6e11c7-3ac9-428d-9a22-21e6d343852f
  spec:
    sourcePod: network-check-source-6f78d59f99-rmpxf
    targetEndpoint: a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:50:33Z"
      message: 'load-balancer-api-internal: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 50.135373ms
      message: 'load-balancer-api-internal: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:33Z"
    - latency: 6.657775ms
      message: 'load-balancer-api-internal: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:33Z"
    - latency: 50.097322ms
      message: 'load-balancer-api-internal: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:33Z"
    - latency: 6.784725ms
      message: 'load-balancer-api-internal: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:33Z"
    - latency: 54.976706ms
      message: 'load-balancer-api-internal: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 7.293646ms
      message: 'load-balancer-api-internal: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 50.890249ms
      message: 'load-balancer-api-internal: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 6.914907ms
      message: 'load-balancer-api-internal: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 55.760701ms
      message: 'load-balancer-api-internal: tcp connection to a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:33Z"
    - latency: 11.70431ms
      message: 'load-balancer-api-internal: resolved host name a004d3cd47af64f05b1402e813782859-9b2f76aefe485d1f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:52:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:44:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-60-to-network-check-target-ip-10-0-130-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-60.us-west-2.compute.internal
      uid: 225a7db9-2dd0-4d43-b9f6-66d929e8bb92
    resourceVersion: "112459"
    uid: ab4e0680-43a6-42a6-9095-4c753be40ac3
  spec:
    sourcePod: network-check-source-6f78d59f99-rmpxf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:51:33Z"
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.098597ms
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 1.063911ms
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 962.589µs
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:33Z"
    - latency: 1.537623ms
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:33Z"
    - latency: 1.039037ms
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:33Z"
    - latency: 1.180998ms
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:33Z"
    - latency: 863.685µs
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:33Z"
    - latency: 990.325µs
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:33Z"
    - latency: 1.286722ms
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:46:33Z"
    - latency: 973.889µs
      message: 'network-check-target-ip-10-0-130-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:45:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:44:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-60-to-network-check-target-ip-10-0-131-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-60.us-west-2.compute.internal
      uid: 225a7db9-2dd0-4d43-b9f6-66d929e8bb92
    resourceVersion: "112458"
    uid: 249ab658-bb3c-4d1b-bc64-2cbb336dd79a
  spec:
    sourcePod: network-check-source-6f78d59f99-rmpxf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:51:33Z"
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.180525ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 2.138913ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 2.34369ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:33Z"
    - latency: 2.276752ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:33Z"
    - latency: 2.543542ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:33Z"
    - latency: 2.293111ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:33Z"
    - latency: 2.204126ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:33Z"
    - latency: 2.810911ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:33Z"
    - latency: 2.126325ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:46:33Z"
    - latency: 2.142624ms
      message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:45:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:44:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-60-to-network-check-target-ip-10-0-139-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-60.us-west-2.compute.internal
      uid: 225a7db9-2dd0-4d43-b9f6-66d929e8bb92
    resourceVersion: "112460"
    uid: 643391e4-b154-4088-9d21-0b4c33d32124
  spec:
    sourcePod: network-check-source-6f78d59f99-rmpxf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:51:33Z"
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.118266ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 2.383344ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 2.267644ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:33Z"
    - latency: 2.128906ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:33Z"
    - latency: 2.645333ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:33Z"
    - latency: 2.497982ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:33Z"
    - latency: 2.204328ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:33Z"
    - latency: 3.330811ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:33Z"
    - latency: 2.286399ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:46:33Z"
    - latency: 2.001939ms
      message: 'network-check-target-ip-10-0-139-66: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:45:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:44:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-60-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-60.us-west-2.compute.internal
      uid: 225a7db9-2dd0-4d43-b9f6-66d929e8bb92
    resourceVersion: "113520"
    uid: 06c3af14-69b8-48dd-b2d1-b3b5a0579102
  spec:
    sourcePod: network-check-source-6f78d59f99-rmpxf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:50:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.282µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:33Z"
    - latency: 1.885434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:33Z"
    - latency: 951.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:33Z"
    - latency: 2.650964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:33Z"
    - latency: 1.031885ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 2.118079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:33Z"
    - latency: 1.312183ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 1.906181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:33Z"
    - latency: 994.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:33Z"
    - latency: 1.834579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:52:33Z"
kind: List
metadata:
  resourceVersion: ""