apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: d87bfc1a-3e94-4e3b-bbe4-8243cee24a09
    resourceVersion: "18568"
    uid: da5bc0d7-849b-4de6-a434-f55227e308e9
  spec:
    sourcePod: network-check-source-6f78d59f99-6gjqc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.756µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:05Z"
    - latency: 1.105488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:05Z"
    - latency: 837.077µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 1.092344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 1.208111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 1.761721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 1.128838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:02:05Z"
    - latency: 1.099649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:01:05Z"
    - latency: 872.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:00:05Z"
    - latency: 1.476402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:59:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: d87bfc1a-3e94-4e3b-bbe4-8243cee24a09
    resourceVersion: "17838"
    uid: 9adeab5f-85a9-44dd-9e31-61db340b92a6
  spec:
    sourcePod: network-check-source-6f78d59f99-6gjqc
    targetEndpoint: a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:00:05Z"
      message: 'load-balancer-api-external: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.926565ms
      message: 'load-balancer-api-external: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 11.084769ms
      message: 'load-balancer-api-external: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 17.274789ms
      message: 'load-balancer-api-external: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 7.972764ms
      message: 'load-balancer-api-external: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 17.429792ms
      message: 'load-balancer-api-external: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 7.639677ms
      message: 'load-balancer-api-external: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 15.702794ms
      message: 'load-balancer-api-external: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 7.709777ms
      message: 'load-balancer-api-external: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 17.239447ms
      message: 'load-balancer-api-external: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:02:05Z"
    - latency: 8.147357ms
      message: 'load-balancer-api-external: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: d87bfc1a-3e94-4e3b-bbe4-8243cee24a09
    resourceVersion: "17839"
    uid: 561e2db9-bc68-4e84-8d62-40973409697b
  spec:
    sourcePod: network-check-source-6f78d59f99-6gjqc
    targetEndpoint: a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:00:05Z"
      message: 'load-balancer-api-internal: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.790416ms
      message: 'load-balancer-api-internal: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 11.006638ms
      message: 'load-balancer-api-internal: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 17.222453ms
      message: 'load-balancer-api-internal: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 8.00057ms
      message: 'load-balancer-api-internal: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 17.411226ms
      message: 'load-balancer-api-internal: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 7.547192ms
      message: 'load-balancer-api-internal: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 15.664708ms
      message: 'load-balancer-api-internal: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 7.767071ms
      message: 'load-balancer-api-internal: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 16.632163ms
      message: 'load-balancer-api-internal: tcp connection to a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:02:05Z"
    - latency: 8.086603ms
      message: 'load-balancer-api-internal: resolved host name a9be57ff00f6b4f9ab569b59fac22ae6-4ef9c870e5d3f43d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-ip-10-0-136-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: d87bfc1a-3e94-4e3b-bbe4-8243cee24a09
    resourceVersion: "18567"
    uid: 93fed7a5-12d6-4824-a647-a38177b1e83d
  spec:
    sourcePod: network-check-source-6f78d59f99-6gjqc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:05Z"
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.315338ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:05Z"
    - latency: 2.48687ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:05Z"
    - latency: 2.230983ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 2.25717ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 2.18146ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 2.276029ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 2.267242ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:02:05Z"
    - latency: 2.266646ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:01:05Z"
    - latency: 2.042292ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:00:05Z"
    - latency: 1.902431ms
      message: 'network-check-target-ip-10-0-136-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:59:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-ip-10-0-140-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: d87bfc1a-3e94-4e3b-bbe4-8243cee24a09
    resourceVersion: "18609"
    uid: 8a695ef1-e851-4459-8ce0-2c5f7046d524
  spec:
    sourcePod: network-check-source-6f78d59f99-6gjqc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:12Z"
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.468µs
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:12Z"
    - latency: 815.235µs
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:12Z"
    - latency: 839.212µs
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:12Z"
    - latency: 2.246339ms
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:12Z"
    - latency: 2.252233ms
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:12Z"
    - latency: 2.218836ms
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:12Z"
    - latency: 2.088773ms
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:02:12Z"
    - latency: 841.856µs
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:01:12Z"
    - latency: 2.024113ms
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:00:12Z"
    - latency: 1.681978ms
      message: 'network-check-target-ip-10-0-140-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:59:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-ip-10-0-143-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: d87bfc1a-3e94-4e3b-bbe4-8243cee24a09
    resourceVersion: "18566"
    uid: 191cb3ea-33b1-490c-bda4-c8b6d7635ff8
  spec:
    sourcePod: network-check-source-6f78d59f99-6gjqc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:05Z"
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.865µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:08:05Z"
    - latency: 780.692µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:07:05Z"
    - latency: 913.499µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 817.097µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 1.172244ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 1.351754ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 1.293312ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:02:05Z"
    - latency: 867.958µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:01:05Z"
    - latency: 1.253931ms
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:00:05Z"
    - latency: 801.862µs
      message: 'network-check-target-ip-10-0-143-198: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:59:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-198-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-198.ec2.internal
      uid: d87bfc1a-3e94-4e3b-bbe4-8243cee24a09
    resourceVersion: "17837"
    uid: 1f077b04-d564-4016-a022-dabc1a7a697e
  spec:
    sourcePod: network-check-source-6f78d59f99-6gjqc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:00:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.881241ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 1.653116ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:06:05Z"
    - latency: 736.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 1.774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:05:05Z"
    - latency: 812.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 1.556638ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:04:05Z"
    - latency: 939.844µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 1.497011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:03:05Z"
    - latency: 729.377µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:02:05Z"
    - latency: 2.070309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:02:05Z"
kind: List
metadata:
  resourceVersion: ""