apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T09:51:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.us-west-1.compute.internal
      uid: a6777bed-ce94-4071-9db8-96dff35545b6
    resourceVersion: "20260"
    uid: bce904ea-de7b-41d1-935c-65b4c3eac846
  spec:
    sourcePod: network-check-source-6f78d59f99-86747
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T09:58:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.879098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 940.927µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 1.168503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:17:26Z"
    - latency: 1.336648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:16:26Z"
    - latency: 1.901258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:15:26Z"
    - latency: 1.164191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:14:26Z"
    - latency: 1.441628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:13:26Z"
    - latency: 1.150767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:12:26Z"
    - latency: 976.649µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:11:26Z"
    - latency: 1.124162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:10:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T09:51:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.us-west-1.compute.internal
      uid: a6777bed-ce94-4071-9db8-96dff35545b6
    resourceVersion: "21015"
    uid: f0afca1f-a1a8-4a09-bcd3-e160d3e9a38b
  spec:
    sourcePod: network-check-source-6f78d59f99-86747
    targetEndpoint: ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T09:57:26Z"
      message: 'load-balancer-api-external: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.038372ms
      message: 'load-balancer-api-external: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:21:26Z"
    - latency: 6.14339ms
      message: 'load-balancer-api-external: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:21:26Z"
    - latency: 54.804909ms
      message: 'load-balancer-api-external: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:20:26Z"
    - latency: 7.621814ms
      message: 'load-balancer-api-external: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:20:26Z"
    - latency: 53.629839ms
      message: 'load-balancer-api-external: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 6.639315ms
      message: 'load-balancer-api-external: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 54.191009ms
      message: 'load-balancer-api-external: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 8.521489ms
      message: 'load-balancer-api-external: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 54.380321ms
      message: 'load-balancer-api-external: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:17:26Z"
    - latency: 6.994724ms
      message: 'load-balancer-api-external: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:17:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T09:51:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.us-west-1.compute.internal
      uid: a6777bed-ce94-4071-9db8-96dff35545b6
    resourceVersion: "21016"
    uid: a24306a7-23ad-4e97-ae11-ef3ef2e6eeda
  spec:
    sourcePod: network-check-source-6f78d59f99-86747
    targetEndpoint: ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T09:57:26Z"
      message: 'load-balancer-api-internal: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.046152ms
      message: 'load-balancer-api-internal: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:21:26Z"
    - latency: 6.016953ms
      message: 'load-balancer-api-internal: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:21:26Z"
    - latency: 54.863473ms
      message: 'load-balancer-api-internal: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:20:26Z"
    - latency: 7.63164ms
      message: 'load-balancer-api-internal: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:20:26Z"
    - latency: 53.615835ms
      message: 'load-balancer-api-internal: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 6.540676ms
      message: 'load-balancer-api-internal: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 54.199043ms
      message: 'load-balancer-api-internal: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 8.480908ms
      message: 'load-balancer-api-internal: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 54.352502ms
      message: 'load-balancer-api-internal: tcp connection to ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:17:26Z"
    - latency: 7.037964ms
      message: 'load-balancer-api-internal: resolved host name ae2b5c469a3734628b463e35f625b60c-40fc92631ddd9ea9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:17:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T09:51:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-ip-10-0-130-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.us-west-1.compute.internal
      uid: a6777bed-ce94-4071-9db8-96dff35545b6
    resourceVersion: "20259"
    uid: a3c252e2-f768-4af7-9b5b-a0023468c01c
  spec:
    sourcePod: network-check-source-6f78d59f99-86747
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T09:58:26Z"
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.002782ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 2.107566ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 1.965047ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:17:26Z"
    - latency: 1.756463ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:16:26Z"
    - latency: 2.278981ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:15:26Z"
    - latency: 1.861925ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:14:26Z"
    - latency: 1.833677ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:13:26Z"
    - latency: 2.964407ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:12:26Z"
    - latency: 2.07544ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:11:26Z"
    - latency: 2.025018ms
      message: 'network-check-target-ip-10-0-130-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:10:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T09:51:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-ip-10-0-139-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.us-west-1.compute.internal
      uid: a6777bed-ce94-4071-9db8-96dff35545b6
    resourceVersion: "20257"
    uid: e37f7428-9a70-4728-91c3-f2cc9f5e7098
  spec:
    sourcePod: network-check-source-6f78d59f99-86747
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T09:58:26Z"
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018901ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 980.12µs
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 1.892031ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:17:26Z"
    - latency: 1.705232ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:16:26Z"
    - latency: 2.033231ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:15:26Z"
    - latency: 1.747638ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:14:26Z"
    - latency: 1.343043ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:13:26Z"
    - latency: 2.071425ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:12:26Z"
    - latency: 1.550946ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:11:26Z"
    - latency: 1.437947ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:10:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T09:51:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-ip-10-0-142-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.us-west-1.compute.internal
      uid: a6777bed-ce94-4071-9db8-96dff35545b6
    resourceVersion: "20258"
    uid: ebb9d9fe-9e2a-4ab9-8971-13eb73ec7fde
  spec:
    sourcePod: network-check-source-6f78d59f99-86747
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T09:58:26Z"
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.956171ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 2.232557ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 2.177971ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:17:26Z"
    - latency: 2.100892ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:16:26Z"
    - latency: 3.182878ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:15:26Z"
    - latency: 2.29881ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:14:26Z"
    - latency: 2.601838ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:13:26Z"
    - latency: 2.214031ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:12:26Z"
    - latency: 2.103424ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:11:26Z"
    - latency: 2.214199ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:10:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T09:51:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-238.us-west-1.compute.internal
      uid: a6777bed-ce94-4071-9db8-96dff35545b6
    resourceVersion: "21012"
    uid: 0462a306-c9e2-4da8-bfb9-5810856999d5
  spec:
    sourcePod: network-check-source-6f78d59f99-86747
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T09:57:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.973µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:21:26Z"
    - latency: 1.903434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:21:26Z"
    - latency: 1.078508ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:20:26Z"
    - latency: 1.892467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:20:26Z"
    - latency: 1.133633ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 1.960044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:19:26Z"
    - latency: 872.614µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 1.663065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:18:26Z"
    - latency: 1.116937ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T10:17:26Z"
    - latency: 2.39469ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T10:17:26Z"
kind: List
metadata:
  resourceVersion: ""