apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-165.ec2.internal
      uid: 3ee5a4aa-50dc-48ee-bede-86759c7b9d2a
    resourceVersion: "67813"
    uid: 9aaa2274-653b-402a-a1cb-5666229634cc
  spec:
    sourcePod: network-check-source-6f8b768455-kqg8b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:53:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.066863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 830.139µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 1.664441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 1.142779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:03Z"
    - latency: 1.258219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:03Z"
    - latency: 1.069938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:16:03Z"
    - latency: 1.103723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:15:03Z"
    - latency: 1.164942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:14:03Z"
    - latency: 1.277565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:13:03Z"
    - latency: 1.114179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-165.ec2.internal
      uid: 3ee5a4aa-50dc-48ee-bede-86759c7b9d2a
    resourceVersion: "68758"
    uid: f14dca6f-c7cd-4a0c-ac1e-89e3088bdcbd
  spec:
    sourcePod: network-check-source-6f8b768455-kqg8b
    targetEndpoint: ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:52:03Z"
      message: 'load-balancer-api-external: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.357619ms
      message: 'load-balancer-api-external: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:22:03Z"
    - latency: 8.617769ms
      message: 'load-balancer-api-external: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:22:03Z"
    - latency: 3.791487ms
      message: 'load-balancer-api-external: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 10.575299ms
      message: 'load-balancer-api-external: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 5.321081ms
      message: 'load-balancer-api-external: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 9.443072ms
      message: 'load-balancer-api-external: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 4.656837ms
      message: 'load-balancer-api-external: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 9.692754ms
      message: 'load-balancer-api-external: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 4.575228ms
      message: 'load-balancer-api-external: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:03Z"
    - latency: 10.624855ms
      message: 'load-balancer-api-external: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:18:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-165.ec2.internal
      uid: 3ee5a4aa-50dc-48ee-bede-86759c7b9d2a
    resourceVersion: "68759"
    uid: 524df3b0-ab00-46ce-b6ae-ae4899d64878
  spec:
    sourcePod: network-check-source-6f8b768455-kqg8b
    targetEndpoint: ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:52:03Z"
      message: 'load-balancer-api-internal: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.177799ms
      message: 'load-balancer-api-internal: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:22:03Z"
    - latency: 8.571494ms
      message: 'load-balancer-api-internal: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:22:03Z"
    - latency: 3.421336ms
      message: 'load-balancer-api-internal: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 10.594622ms
      message: 'load-balancer-api-internal: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 4.007865ms
      message: 'load-balancer-api-internal: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 9.527445ms
      message: 'load-balancer-api-internal: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 4.731211ms
      message: 'load-balancer-api-internal: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 9.796321ms
      message: 'load-balancer-api-internal: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 4.480941ms
      message: 'load-balancer-api-internal: tcp connection to ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:03Z"
    - latency: 10.552996ms
      message: 'load-balancer-api-internal: resolved host name ab72ff3f93d654427890d7ed8fbf7ef2-ff5ff146eaba928d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:18:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-165-to-network-check-target-ip-10-0-135-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-165.ec2.internal
      uid: 3ee5a4aa-50dc-48ee-bede-86759c7b9d2a
    resourceVersion: "67812"
    uid: 8b1e65e8-7cb0-47b0-bf7b-31a6fe176656
  spec:
    sourcePod: network-check-source-6f8b768455-kqg8b
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:53:03Z"
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.177395ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 1.974657ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 1.826528ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 2.171869ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:03Z"
    - latency: 2.470257ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:03Z"
    - latency: 2.242724ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:16:03Z"
    - latency: 3.310547ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:15:03Z"
    - latency: 2.344967ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:14:03Z"
    - latency: 2.221703ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:13:03Z"
    - latency: 2.188027ms
      message: 'network-check-target-ip-10-0-135-55: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-165-to-network-check-target-ip-10-0-141-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-165.ec2.internal
      uid: 3ee5a4aa-50dc-48ee-bede-86759c7b9d2a
    resourceVersion: "67811"
    uid: 92f9b7ae-8c6c-4596-ba15-18737e8c9329
  spec:
    sourcePod: network-check-source-6f8b768455-kqg8b
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:53:03Z"
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249954ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 2.466944ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 2.559258ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 2.265935ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:03Z"
    - latency: 2.29309ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:03Z"
    - latency: 2.308225ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:16:03Z"
    - latency: 2.137268ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:15:03Z"
    - latency: 2.300285ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:14:03Z"
    - latency: 2.26223ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:13:03Z"
    - latency: 2.291773ms
      message: 'network-check-target-ip-10-0-141-153: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-165-to-network-check-target-ip-10-0-143-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-165.ec2.internal
      uid: 3ee5a4aa-50dc-48ee-bede-86759c7b9d2a
    resourceVersion: "67810"
    uid: f5f3d3f4-8f34-4572-965f-afe7129ba22e
  spec:
    sourcePod: network-check-source-6f8b768455-kqg8b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:53:03Z"
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.47µs
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 1.449168ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 1.210531ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 987.848µs
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:03Z"
    - latency: 1.00241ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:17:03Z"
    - latency: 1.064317ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:16:03Z"
    - latency: 1.551574ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:15:03Z"
    - latency: 1.043476ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:14:03Z"
    - latency: 1.020101ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:13:03Z"
    - latency: 1.202073ms
      message: 'network-check-target-ip-10-0-143-165: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:46:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-165.ec2.internal
      uid: 3ee5a4aa-50dc-48ee-bede-86759c7b9d2a
    resourceVersion: "68756"
    uid: bcd872f5-3b81-499a-a60d-911f0e49e247
  spec:
    sourcePod: network-check-source-6f8b768455-kqg8b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:52:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104906ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:22:03Z"
    - latency: 2.09545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:22:03Z"
    - latency: 1.04075ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 1.747672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:21:03Z"
    - latency: 852.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 1.885032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:20:03Z"
    - latency: 1.066772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 2.130108ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:19:03Z"
    - latency: 988.886µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:18:03Z"
    - latency: 2.100668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:18:03Z"
kind: List
metadata:
  resourceVersion: ""