apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-24-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-24.ec2.internal
      uid: ac91c3fd-7f80-4c8c-82a6-4c41e0549b8a
    resourceVersion: "44449"
    uid: 3125c9b0-ad13-4104-9222-25ebe01bb151
  spec:
    sourcePod: network-check-source-7f44b6dd87-fxjlj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T22:01:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 784.922µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 915.234µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 1.054578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:20:02Z"
    - latency: 1.112007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:19:02Z"
    - latency: 950.204µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:18:02Z"
    - latency: 738.934µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:17:02Z"
    - latency: 1.367444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:16:02Z"
    - latency: 851.377µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:15:02Z"
    - latency: 927.271µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:02Z"
    - latency: 1.178115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-24-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-24.ec2.internal
      uid: ac91c3fd-7f80-4c8c-82a6-4c41e0549b8a
    resourceVersion: "46618"
    uid: 02d3f326-93ed-48ce-a192-9aab46609fc9
  spec:
    sourcePod: network-check-source-7f44b6dd87-fxjlj
    targetEndpoint: ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T22:00:02Z"
      message: 'load-balancer-api-external: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.101148ms
      message: 'load-balancer-api-external: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:24:02Z"
    - latency: 6.704758ms
      message: 'load-balancer-api-external: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:24:02Z"
    - latency: 4.563787ms
      message: 'load-balancer-api-external: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:23:02Z"
    - latency: 6.813427ms
      message: 'load-balancer-api-external: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:23:02Z"
    - latency: 5.742174ms
      message: 'load-balancer-api-external: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 6.69224ms
      message: 'load-balancer-api-external: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 5.834875ms
      message: 'load-balancer-api-external: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 7.095879ms
      message: 'load-balancer-api-external: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 5.179195ms
      message: 'load-balancer-api-external: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:20:02Z"
    - latency: 7.170863ms
      message: 'load-balancer-api-external: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:20:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-24-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-24.ec2.internal
      uid: ac91c3fd-7f80-4c8c-82a6-4c41e0549b8a
    resourceVersion: "46617"
    uid: 4cb036ca-06ac-4220-8295-c6aa259ce2be
  spec:
    sourcePod: network-check-source-7f44b6dd87-fxjlj
    targetEndpoint: ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T22:00:02Z"
      message: 'load-balancer-api-internal: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.058925ms
      message: 'load-balancer-api-internal: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:24:02Z"
    - latency: 6.653672ms
      message: 'load-balancer-api-internal: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:24:02Z"
    - latency: 3.654489ms
      message: 'load-balancer-api-internal: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:23:02Z"
    - latency: 6.851278ms
      message: 'load-balancer-api-internal: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:23:02Z"
    - latency: 5.785798ms
      message: 'load-balancer-api-internal: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 6.632171ms
      message: 'load-balancer-api-internal: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 5.181991ms
      message: 'load-balancer-api-internal: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 7.147474ms
      message: 'load-balancer-api-internal: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 3.370456ms
      message: 'load-balancer-api-internal: tcp connection to ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:20:02Z"
    - latency: 7.318605ms
      message: 'load-balancer-api-internal: resolved host name ad442995c987f479bbfc14c171924c12-c25536eee5a8225b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:20:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-129-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-24.ec2.internal
      uid: ac91c3fd-7f80-4c8c-82a6-4c41e0549b8a
    resourceVersion: "44447"
    uid: 5814ead3-dc81-4677-aa82-2db01cc18163
  spec:
    sourcePod: network-check-source-7f44b6dd87-fxjlj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T22:01:02Z"
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.148884ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 2.365371ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 2.041396ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:20:02Z"
    - latency: 2.004983ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:19:02Z"
    - latency: 2.115744ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:18:02Z"
    - latency: 2.228581ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:17:02Z"
    - latency: 2.202955ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:16:02Z"
    - latency: 1.909808ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:15:02Z"
    - latency: 2.11622ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:02Z"
    - latency: 2.208981ms
      message: 'network-check-target-ip-10-0-129-137: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-131-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-24.ec2.internal
      uid: ac91c3fd-7f80-4c8c-82a6-4c41e0549b8a
    resourceVersion: "44448"
    uid: 0b5cce73-5893-4ca1-b0ba-64b654c909d4
  spec:
    sourcePod: network-check-source-7f44b6dd87-fxjlj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T22:01:02Z"
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.209464ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 1.981088ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 1.711351ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:20:02Z"
    - latency: 2.022129ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:19:02Z"
    - latency: 2.18175ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:18:02Z"
    - latency: 2.177143ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:17:02Z"
    - latency: 2.343127ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:16:02Z"
    - latency: 2.77694ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:15:02Z"
    - latency: 2.101383ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:02Z"
    - latency: 2.027548ms
      message: 'network-check-target-ip-10-0-131-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-135-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-24.ec2.internal
      uid: ac91c3fd-7f80-4c8c-82a6-4c41e0549b8a
    resourceVersion: "44446"
    uid: 1cd6aac9-d8e0-4fb3-838f-f3e341c0a808
  spec:
    sourcePod: network-check-source-7f44b6dd87-fxjlj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T22:01:02Z"
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 801.48µs
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 1.136335ms
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 791.697µs
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:20:02Z"
    - latency: 960.799µs
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:19:02Z"
    - latency: 1.343712ms
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:18:02Z"
    - latency: 1.415151ms
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:17:02Z"
    - latency: 811.186µs
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:16:02Z"
    - latency: 895.779µs
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:15:02Z"
    - latency: 1.325826ms
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:14:02Z"
    - latency: 855.781µs
      message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:13:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-20T21:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-24-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-24.ec2.internal
      uid: ac91c3fd-7f80-4c8c-82a6-4c41e0549b8a
    resourceVersion: "46616"
    uid: b962eb4d-c90e-4a31-af27-b11dc7a38405
  spec:
    sourcePod: network-check-source-7f44b6dd87-fxjlj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-20T22:00:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 867.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:24:02Z"
    - latency: 1.666407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:24:02Z"
    - latency: 1.065455ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:23:02Z"
    - latency: 1.817506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:23:02Z"
    - latency: 917.13µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 1.846431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:22:02Z"
    - latency: 893.574µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 2.470319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:21:02Z"
    - latency: 1.164056ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-20T22:20:02Z"
    - latency: 1.869369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-20T22:20:02Z"
kind: List
metadata:
  resourceVersion: ""