apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-139.ec2.internal
      uid: 71af872e-e50e-4358-901c-e0e8a82df8a9
    resourceVersion: "34458"
    uid: 564a2813-e997-4488-a49b-1caed8fe3c5a
  spec:
    sourcePod: network-check-source-6f8b768455-npbm5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.088408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:40:55Z"
    - latency: 1.036001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 1.281378ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 1.006238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 996.41µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 1.70391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:35:55Z"
    - latency: 1.724401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:34:55Z"
    - latency: 981.255µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:33:55Z"
    - latency: 1.064699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:32:55Z"
    - latency: 935.994µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:31:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-139.ec2.internal
      uid: 71af872e-e50e-4358-901c-e0e8a82df8a9
    resourceVersion: "34041"
    uid: 6f44a4bb-ee57-4eb0-a5fa-e155a7c1e467
  spec:
    sourcePod: network-check-source-6f8b768455-npbm5
    targetEndpoint: ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:55Z"
      message: 'load-balancer-api-external: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.35164ms
      message: 'load-balancer-api-external: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 9.349944ms
      message: 'load-balancer-api-external: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 4.837229ms
      message: 'load-balancer-api-external: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 9.167734ms
      message: 'load-balancer-api-external: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 4.918012ms
      message: 'load-balancer-api-external: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 8.351148ms
      message: 'load-balancer-api-external: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 5.126931ms
      message: 'load-balancer-api-external: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 10.841095ms
      message: 'load-balancer-api-external: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 4.473947ms
      message: 'load-balancer-api-external: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:35:55Z"
    - latency: 12.455972ms
      message: 'load-balancer-api-external: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:35:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-139.ec2.internal
      uid: 71af872e-e50e-4358-901c-e0e8a82df8a9
    resourceVersion: "34042"
    uid: bc751b87-ac1c-4970-a386-69baedbcd2ce
  spec:
    sourcePod: network-check-source-6f8b768455-npbm5
    targetEndpoint: ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:55Z"
      message: 'load-balancer-api-internal: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.031643ms
      message: 'load-balancer-api-internal: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 9.403269ms
      message: 'load-balancer-api-internal: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 4.818575ms
      message: 'load-balancer-api-internal: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 9.08336ms
      message: 'load-balancer-api-internal: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 4.933812ms
      message: 'load-balancer-api-internal: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 8.442153ms
      message: 'load-balancer-api-internal: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 5.163068ms
      message: 'load-balancer-api-internal: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 10.781811ms
      message: 'load-balancer-api-internal: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 3.542535ms
      message: 'load-balancer-api-internal: tcp connection to ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:35:55Z"
    - latency: 12.515824ms
      message: 'load-balancer-api-internal: resolved host name ac70b8e70040946f3b6d120050bd2273-c089c42ca02beb37.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:35:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-139-to-network-check-target-ip-10-0-137-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-139.ec2.internal
      uid: 71af872e-e50e-4358-901c-e0e8a82df8a9
    resourceVersion: "34457"
    uid: 572f37f4-426e-43a2-9631-745405c8897e
  spec:
    sourcePod: network-check-source-6f8b768455-npbm5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:55Z"
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.383994ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:40:55Z"
    - latency: 2.335505ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 2.124471ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 2.085649ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 2.285908ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 2.336147ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:35:55Z"
    - latency: 2.219948ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:34:55Z"
    - latency: 2.398121ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:33:55Z"
    - latency: 2.281961ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:32:55Z"
    - latency: 2.025702ms
      message: 'network-check-target-ip-10-0-137-26: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:31:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-139-to-network-check-target-ip-10-0-139-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-139.ec2.internal
      uid: 71af872e-e50e-4358-901c-e0e8a82df8a9
    resourceVersion: "34456"
    uid: 94ea9a4f-aba1-4cb1-b0f3-540985a1fb32
  spec:
    sourcePod: network-check-source-6f8b768455-npbm5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:55Z"
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.285488ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:40:55Z"
    - latency: 2.199742ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 2.129765ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 2.001926ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 2.204957ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 2.243534ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:35:55Z"
    - latency: 2.431024ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:34:55Z"
    - latency: 2.463617ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:33:55Z"
    - latency: 2.154436ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:32:55Z"
    - latency: 2.215087ms
      message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:31:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-139-to-network-check-target-ip-10-0-141-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-139.ec2.internal
      uid: 71af872e-e50e-4358-901c-e0e8a82df8a9
    resourceVersion: "34455"
    uid: 811faa08-2275-41e6-a80f-cafd6786b092
  spec:
    sourcePod: network-check-source-6f8b768455-npbm5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:55Z"
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.176208ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:40:55Z"
    - latency: 948.181µs
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 1.478256ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 996.654µs
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 1.010853ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 998.111µs
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:35:55Z"
    - latency: 889.94µs
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:34:55Z"
    - latency: 881.651µs
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:33:55Z"
    - latency: 996.96µs
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:32:55Z"
    - latency: 1.362049ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:31:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-139.ec2.internal
      uid: 71af872e-e50e-4358-901c-e0e8a82df8a9
    resourceVersion: "34040"
    uid: c176f331-b9eb-4ec4-8540-d88c914cb535
  spec:
    sourcePod: network-check-source-6f8b768455-npbm5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.150002ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 1.952078ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:39:55Z"
    - latency: 898.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 1.681362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:38:55Z"
    - latency: 1.318239ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 1.699036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:37:55Z"
    - latency: 849.937µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 1.743396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:36:55Z"
    - latency: 904.928µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:35:55Z"
    - latency: 2.178902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:35:55Z"
kind: List
metadata:
  resourceVersion: ""