apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T03:45:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: b016707e-d0b4-455f-be25-6cf12432404d
    resourceVersion: "47069"
    uid: 4cb4a6c9-7c7d-4eaf-97e6-6644217a36a0
  spec:
    sourcePod: network-check-source-989f8b8dc-vh66t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T03:52:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.010257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 1.062169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 1.425312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:11:44Z"
    - latency: 1.118231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:10:44Z"
    - latency: 1.195645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:09:44Z"
    - latency: 817.165µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:08:44Z"
    - latency: 1.124952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:07:44Z"
    - latency: 979.673µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:06:44Z"
    - latency: 1.133921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:05:44Z"
    - latency: 1.162342ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:04:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T03:45:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: b016707e-d0b4-455f-be25-6cf12432404d
    resourceVersion: "49610"
    uid: 16c49db4-eb90-4185-a12c-9fda606f9734
  spec:
    sourcePod: network-check-source-989f8b8dc-vh66t
    targetEndpoint: abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T03:51:44Z"
      message: 'load-balancer-api-external: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.289409ms
      message: 'load-balancer-api-external: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:15:44Z"
    - latency: 6.978844ms
      message: 'load-balancer-api-external: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:15:44Z"
    - latency: 5.136815ms
      message: 'load-balancer-api-external: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:14:44Z"
    - latency: 7.244267ms
      message: 'load-balancer-api-external: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:14:44Z"
    - latency: 4.501816ms
      message: 'load-balancer-api-external: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 7.905291ms
      message: 'load-balancer-api-external: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 5.128752ms
      message: 'load-balancer-api-external: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 6.130529ms
      message: 'load-balancer-api-external: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 5.339272ms
      message: 'load-balancer-api-external: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:11:44Z"
    - latency: 6.835527ms
      message: 'load-balancer-api-external: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:11:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T03:45:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: b016707e-d0b4-455f-be25-6cf12432404d
    resourceVersion: "49611"
    uid: 70044e18-2ae1-46d1-9063-066b5448c63f
  spec:
    sourcePod: network-check-source-989f8b8dc-vh66t
    targetEndpoint: abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T03:51:44Z"
      message: 'load-balancer-api-internal: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.384163ms
      message: 'load-balancer-api-internal: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:15:44Z"
    - latency: 7.042285ms
      message: 'load-balancer-api-internal: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:15:44Z"
    - latency: 5.122626ms
      message: 'load-balancer-api-internal: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:14:44Z"
    - latency: 7.303905ms
      message: 'load-balancer-api-internal: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:14:44Z"
    - latency: 4.339295ms
      message: 'load-balancer-api-internal: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 7.85653ms
      message: 'load-balancer-api-internal: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 5.142228ms
      message: 'load-balancer-api-internal: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 6.23444ms
      message: 'load-balancer-api-internal: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 5.363066ms
      message: 'load-balancer-api-internal: tcp connection to abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:11:44Z"
    - latency: 6.88827ms
      message: 'load-balancer-api-internal: resolved host name abe2768fcbc4b44c2a8b89aec8eddfc3-e2808e66008033a6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:11:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T03:45:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-ip-10-0-134-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: b016707e-d0b4-455f-be25-6cf12432404d
    resourceVersion: "47068"
    uid: c0279caf-4eeb-48e8-969b-c7d187106f10
  spec:
    sourcePod: network-check-source-989f8b8dc-vh66t
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T03:52:44Z"
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.50424ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 2.253194ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 2.488689ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:11:44Z"
    - latency: 2.305394ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:10:44Z"
    - latency: 2.458622ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:09:44Z"
    - latency: 2.439813ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:08:44Z"
    - latency: 2.245192ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:07:44Z"
    - latency: 2.419766ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:06:44Z"
    - latency: 2.221872ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:05:44Z"
    - latency: 2.41755ms
      message: 'network-check-target-ip-10-0-134-164: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:04:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T03:45:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-ip-10-0-137-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: b016707e-d0b4-455f-be25-6cf12432404d
    resourceVersion: "47066"
    uid: 82ed37f7-252b-4b7e-8f80-e8334a52fff6
  spec:
    sourcePod: network-check-source-989f8b8dc-vh66t
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T03:52:44Z"
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024684ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 1.001962ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 916.017µs
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:11:44Z"
    - latency: 989.424µs
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:10:44Z"
    - latency: 1.425514ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:09:44Z"
    - latency: 995.244µs
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:08:44Z"
    - latency: 1.334526ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:07:44Z"
    - latency: 869.275µs
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:06:44Z"
    - latency: 845.917µs
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:05:44Z"
    - latency: 875.663µs
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:04:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T03:45:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-ip-10-0-143-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: b016707e-d0b4-455f-be25-6cf12432404d
    resourceVersion: "47067"
    uid: a1c2520c-1845-448a-b98e-99c6e72f2e73
  spec:
    sourcePod: network-check-source-989f8b8dc-vh66t
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T03:52:44Z"
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.921008ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 1.845965ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 2.117085ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:11:44Z"
    - latency: 1.824139ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:10:44Z"
    - latency: 1.989807ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:09:44Z"
    - latency: 1.972612ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:08:44Z"
    - latency: 1.999606ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:07:44Z"
    - latency: 1.956858ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:06:44Z"
    - latency: 2.136365ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:05:44Z"
    - latency: 2.379947ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:04:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T03:45:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: b016707e-d0b4-455f-be25-6cf12432404d
    resourceVersion: "49609"
    uid: 8e51a0ec-c785-47cf-b189-8c2f2ea1fdbd
  spec:
    sourcePod: network-check-source-989f8b8dc-vh66t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T03:51:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.045328ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:15:44Z"
    - latency: 1.794755ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:15:44Z"
    - latency: 813.753µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:14:44Z"
    - latency: 1.921341ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:14:44Z"
    - latency: 699.761µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 1.993162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:13:44Z"
    - latency: 865.38µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 1.867647ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:12:44Z"
    - latency: 1.034239ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:11:44Z"
    - latency: 1.899871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:11:44Z"
kind: List
metadata:
  resourceVersion: ""