apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-158-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-158.ec2.internal
      uid: 44cf587f-543b-44e8-a971-62e5694c4264
    resourceVersion: "31997"
    uid: 51a800e8-86f6-4266-814f-a15b2c6c7719
  spec:
    sourcePod: network-check-source-989f8b8dc-4jf9k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06: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.105003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 1.007263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 1.200258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 1.423754ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 1.658726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:55Z"
    - latency: 1.365208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:55Z"
    - latency: 961.612µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:55Z"
    - latency: 1.063747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:55Z"
    - latency: 956.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:55Z"
    - latency: 884.984µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-158-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-158.ec2.internal
      uid: 44cf587f-543b-44e8-a971-62e5694c4264
    resourceVersion: "31998"
    uid: f75c10f1-7915-4f08-a477-cc41a8ae85c5
  spec:
    sourcePod: network-check-source-989f8b8dc-4jf9k
    targetEndpoint: a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:05:55Z"
      message: 'load-balancer-api-external: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.019106ms
      message: 'load-balancer-api-external: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 8.989846ms
      message: 'load-balancer-api-external: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 4.452216ms
      message: 'load-balancer-api-external: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 8.37803ms
      message: 'load-balancer-api-external: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 6.397932ms
      message: 'load-balancer-api-external: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 7.976525ms
      message: 'load-balancer-api-external: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 5.23078ms
      message: 'load-balancer-api-external: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 9.900214ms
      message: 'load-balancer-api-external: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 5.399872ms
      message: 'load-balancer-api-external: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:55Z"
    - latency: 9.108229ms
      message: 'load-balancer-api-external: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:37:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-158-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-158.ec2.internal
      uid: 44cf587f-543b-44e8-a971-62e5694c4264
    resourceVersion: "31999"
    uid: 94c9786c-c14c-4074-bb85-1171941d376d
  spec:
    sourcePod: network-check-source-989f8b8dc-4jf9k
    targetEndpoint: a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:05:55Z"
      message: 'load-balancer-api-internal: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.231106ms
      message: 'load-balancer-api-internal: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 8.962827ms
      message: 'load-balancer-api-internal: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 4.54066ms
      message: 'load-balancer-api-internal: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 8.433123ms
      message: 'load-balancer-api-internal: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 5.738992ms
      message: 'load-balancer-api-internal: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 8.118412ms
      message: 'load-balancer-api-internal: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 5.20497ms
      message: 'load-balancer-api-internal: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 9.96589ms
      message: 'load-balancer-api-internal: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 5.09182ms
      message: 'load-balancer-api-internal: tcp connection to a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:55Z"
    - latency: 9.162535ms
      message: 'load-balancer-api-internal: resolved host name a14015b673e2c413db070b5bb8999aa7-39028a6a2a7620f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:37:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-158-to-network-check-target-ip-10-0-128-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-158.ec2.internal
      uid: 44cf587f-543b-44e8-a971-62e5694c4264
    resourceVersion: "31995"
    uid: 8324d8e3-a62e-4f24-ad60-0fe680f77f8e
  spec:
    sourcePod: network-check-source-989f8b8dc-4jf9k
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06:55Z"
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.475107ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 2.162753ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 2.245086ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 2.202035ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 2.528249ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:55Z"
    - latency: 2.282469ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:55Z"
    - latency: 2.196983ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:55Z"
    - latency: 2.353383ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:55Z"
    - latency: 2.228239ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:55Z"
    - latency: 2.370253ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-158-to-network-check-target-ip-10-0-130-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-158.ec2.internal
      uid: 44cf587f-543b-44e8-a971-62e5694c4264
    resourceVersion: "31994"
    uid: 452d9ed1-c181-40dd-8d97-0d55287d6dff
  spec:
    sourcePod: network-check-source-989f8b8dc-4jf9k
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06:55Z"
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.350937ms
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 951.56µs
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 887.196µs
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 1.527405ms
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 2.342632ms
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:55Z"
    - latency: 962.95µs
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:55Z"
    - latency: 999.172µs
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:55Z"
    - latency: 876.785µs
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:55Z"
    - latency: 905.378µs
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:55Z"
    - latency: 954.539µs
      message: 'network-check-target-ip-10-0-130-158: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-158-to-network-check-target-ip-10-0-134-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-158.ec2.internal
      uid: 44cf587f-543b-44e8-a971-62e5694c4264
    resourceVersion: "31993"
    uid: fc60e5fe-b7f9-4e64-a0ca-1838c00be69a
  spec:
    sourcePod: network-check-source-989f8b8dc-4jf9k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:06:55Z"
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.145214ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 2.253048ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 2.327697ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 2.22533ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 2.316141ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:55Z"
    - latency: 2.026048ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:36:55Z"
    - latency: 2.247461ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:35:55Z"
    - latency: 2.466085ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:34:55Z"
    - latency: 2.048378ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:33:55Z"
    - latency: 2.093448ms
      message: 'network-check-target-ip-10-0-134-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:32:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:59:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-158-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-158.ec2.internal
      uid: 44cf587f-543b-44e8-a971-62e5694c4264
    resourceVersion: "31996"
    uid: b7945a08-95fe-4bfa-8dbb-b6f861375d3e
  spec:
    sourcePod: network-check-source-989f8b8dc-4jf9k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T15:05:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.773µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 1.830625ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:41:55Z"
    - latency: 747.54µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 1.646724ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:40:55Z"
    - latency: 876.867µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 1.638855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:39:55Z"
    - latency: 797.708µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 1.717968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:38:55Z"
    - latency: 975.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:37:55Z"
    - latency: 1.793898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:37:55Z"
kind: List
metadata:
  resourceVersion: ""