apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-23T02:40:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-146.ec2.internal
      uid: a3eceb9e-413e-49d0-9308-bf62434475d9
    resourceVersion: "34931"
    uid: 15d4a794-0fb0-4d87-bf16-7ff1fb0a6388
  spec:
    sourcePod: network-check-source-757774bcb8-mv5tm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-23T02:47:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 1.13443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 1.082518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 1.276607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:54:54Z"
    - latency: 1.103164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:53:54Z"
    - latency: 1.753225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:52:54Z"
    - latency: 924.331µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:51:54Z"
    - latency: 928.348µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:50:54Z"
    - latency: 1.32844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:49:54Z"
    - latency: 1.196441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-23T02:40:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-146.ec2.internal
      uid: a3eceb9e-413e-49d0-9308-bf62434475d9
    resourceVersion: "35713"
    uid: adf44058-f18f-4d9f-843f-d66bf990dd0a
  spec:
    sourcePod: network-check-source-757774bcb8-mv5tm
    targetEndpoint: a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-23T02:46:54Z"
      message: 'load-balancer-api-external: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.020121ms
      message: 'load-balancer-api-external: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:58:54Z"
    - latency: 10.426269ms
      message: 'load-balancer-api-external: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:58:54Z"
    - latency: 16.793304ms
      message: 'load-balancer-api-external: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 10.894979ms
      message: 'load-balancer-api-external: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 16.242572ms
      message: 'load-balancer-api-external: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 10.651966ms
      message: 'load-balancer-api-external: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 16.836655ms
      message: 'load-balancer-api-external: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 14.193921ms
      message: 'load-balancer-api-external: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 18.356324ms
      message: 'load-balancer-api-external: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:54:54Z"
    - latency: 8.337632ms
      message: 'load-balancer-api-external: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:54:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-23T02:40:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-146.ec2.internal
      uid: a3eceb9e-413e-49d0-9308-bf62434475d9
    resourceVersion: "35712"
    uid: 0a47de67-491e-4786-a0c6-cbe63e4f1887
  spec:
    sourcePod: network-check-source-757774bcb8-mv5tm
    targetEndpoint: a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-23T02:46:54Z"
      message: 'load-balancer-api-internal: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.946558ms
      message: 'load-balancer-api-internal: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:58:54Z"
    - latency: 10.363525ms
      message: 'load-balancer-api-internal: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:58:54Z"
    - latency: 15.867791ms
      message: 'load-balancer-api-internal: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 10.917993ms
      message: 'load-balancer-api-internal: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 17.898388ms
      message: 'load-balancer-api-internal: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 10.633138ms
      message: 'load-balancer-api-internal: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 18.627044ms
      message: 'load-balancer-api-internal: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 14.13627ms
      message: 'load-balancer-api-internal: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 16.988268ms
      message: 'load-balancer-api-internal: tcp connection to a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:54:54Z"
    - latency: 8.281146ms
      message: 'load-balancer-api-internal: resolved host name a413be742724c4879a79ff5f1c2ce240-2dd8803fdaf02db4.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:54:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-23T02:40:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-146-to-network-check-target-ip-10-0-129-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-146.ec2.internal
      uid: a3eceb9e-413e-49d0-9308-bf62434475d9
    resourceVersion: "34929"
    uid: 0cd6c95d-e4d8-4d15-9e8e-364198812026
  spec:
    sourcePod: network-check-source-757774bcb8-mv5tm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-23T02:47:54Z"
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.031126ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 2.173025ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 2.397105ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 2.134447ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:54:54Z"
    - latency: 2.266718ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:53:54Z"
    - latency: 2.34054ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:52:54Z"
    - latency: 2.229991ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:51:54Z"
    - latency: 2.303764ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:50:54Z"
    - latency: 2.430707ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:49:54Z"
    - latency: 2.473279ms
      message: 'network-check-target-ip-10-0-129-58: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-23T02:40:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-146-to-network-check-target-ip-10-0-140-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-146.ec2.internal
      uid: a3eceb9e-413e-49d0-9308-bf62434475d9
    resourceVersion: "34930"
    uid: d8ebcabd-9e75-4ddd-8b03-f641797ad001
  spec:
    sourcePod: network-check-source-757774bcb8-mv5tm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-23T02:47:54Z"
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.214465ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 1.843288ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 1.951502ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 2.058432ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:54:54Z"
    - latency: 2.021398ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:53:54Z"
    - latency: 2.597ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:52:54Z"
    - latency: 1.867124ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:51:54Z"
    - latency: 1.936337ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:50:54Z"
    - latency: 2.085886ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:49:54Z"
    - latency: 2.103805ms
      message: 'network-check-target-ip-10-0-140-14: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-23T02:40:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-146-to-network-check-target-ip-10-0-140-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-146.ec2.internal
      uid: a3eceb9e-413e-49d0-9308-bf62434475d9
    resourceVersion: "34928"
    uid: 7accfb13-9cf8-4514-ae2e-822cb146a3e5
  spec:
    sourcePod: network-check-source-757774bcb8-mv5tm
    targetEndpoint: 10.132.0.6:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-23T02:47:54Z"
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029849ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 847.913µs
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 1.428784ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 966.68µs
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:54:54Z"
    - latency: 932.215µs
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:53:54Z"
    - latency: 947.925µs
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:52:54Z"
    - latency: 843.43µs
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:51:54Z"
    - latency: 1.070405ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:50:54Z"
    - latency: 1.053145ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:49:54Z"
    - latency: 924.072µs
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.132.0.6:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:48:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-23T02:40:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-146.ec2.internal
      uid: a3eceb9e-413e-49d0-9308-bf62434475d9
    resourceVersion: "35709"
    uid: 754c9855-03ec-4599-8fa4-3e563a38b311
  spec:
    sourcePod: network-check-source-757774bcb8-mv5tm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-23T02:46:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:58:54Z"
    - latency: 1.737457ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:58:54Z"
    - latency: 933.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 1.727984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:57:54Z"
    - latency: 701.732µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 2.277318ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:56:54Z"
    - latency: 961.86µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 2.08607ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:55:54Z"
    - latency: 787.346µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-23T03:54:54Z"
    - latency: 1.938731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-23T03:54:54Z"
kind: List
metadata:
  resourceVersion: ""