apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:57:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: e7ed4025-95cd-4aa0-83a3-1ce3ede5f08d
    resourceVersion: "52721"
    uid: bb94eb32-03e2-492f-ba8e-bfab0090183f
  spec:
    sourcePod: network-check-source-7d88cb55d8-lgmfj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:04:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:09Z"
    - latency: 886.22µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:20:09Z"
    - latency: 822.019µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:19:09Z"
    - latency: 1.091975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:18:09Z"
    - latency: 895.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:17:09Z"
    - latency: 971.059µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:16:09Z"
    - latency: 883.717µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:15:09Z"
    - latency: 913.802µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:14:09Z"
    - latency: 906.378µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:13:09Z"
    - latency: 823.972µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:12:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:57:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: e7ed4025-95cd-4aa0-83a3-1ce3ede5f08d
    resourceVersion: "55753"
    uid: 63d6b2d2-acd4-4a37-bcfe-dac77cca256c
  spec:
    sourcePod: network-check-source-7d88cb55d8-lgmfj
    targetEndpoint: a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:03:09Z"
      message: 'load-balancer-api-external: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.838832ms
      message: 'load-balancer-api-external: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:27:09Z"
    - latency: 8.665951ms
      message: 'load-balancer-api-external: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:27:09Z"
    - latency: 5.519848ms
      message: 'load-balancer-api-external: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:09Z"
    - latency: 6.701016ms
      message: 'load-balancer-api-external: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:26:09Z"
    - latency: 5.011658ms
      message: 'load-balancer-api-external: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:09Z"
    - latency: 7.719312ms
      message: 'load-balancer-api-external: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:25:09Z"
    - latency: 6.155569ms
      message: 'load-balancer-api-external: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:09Z"
    - latency: 7.432488ms
      message: 'load-balancer-api-external: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:24:09Z"
    - latency: 5.355258ms
      message: 'load-balancer-api-external: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:09Z"
    - latency: 7.141631ms
      message: 'load-balancer-api-external: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:23:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:57:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: e7ed4025-95cd-4aa0-83a3-1ce3ede5f08d
    resourceVersion: "55754"
    uid: 16ecf5b0-3ad6-4bbf-8db3-ccc79bcda441
  spec:
    sourcePod: network-check-source-7d88cb55d8-lgmfj
    targetEndpoint: a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:03:09Z"
      message: 'load-balancer-api-internal: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.849828ms
      message: 'load-balancer-api-internal: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:27:09Z"
    - latency: 8.539718ms
      message: 'load-balancer-api-internal: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:27:09Z"
    - latency: 5.52715ms
      message: 'load-balancer-api-internal: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:09Z"
    - latency: 6.584721ms
      message: 'load-balancer-api-internal: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:26:09Z"
    - latency: 6.01138ms
      message: 'load-balancer-api-internal: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:09Z"
    - latency: 7.577229ms
      message: 'load-balancer-api-internal: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:25:09Z"
    - latency: 6.186027ms
      message: 'load-balancer-api-internal: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:09Z"
    - latency: 7.376514ms
      message: 'load-balancer-api-internal: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:24:09Z"
    - latency: 3.318773ms
      message: 'load-balancer-api-internal: tcp connection to a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:09Z"
    - latency: 7.062755ms
      message: 'load-balancer-api-internal: resolved host name a2608ac17d6f94f689a78ffada77731e-f627784c4564bf06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:23:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:57:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-ip-10-0-129-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: e7ed4025-95cd-4aa0-83a3-1ce3ede5f08d
    resourceVersion: "52718"
    uid: d34d1f47-6c88-49b4-91c2-d29add7769eb
  spec:
    sourcePod: network-check-source-7d88cb55d8-lgmfj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:04:09Z"
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.138153ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:09Z"
    - latency: 2.038047ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:20:09Z"
    - latency: 2.349771ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:19:09Z"
    - latency: 2.120513ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:18:09Z"
    - latency: 2.290216ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:17:09Z"
    - latency: 2.100723ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:16:09Z"
    - latency: 2.338053ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:15:09Z"
    - latency: 2.300818ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:14:09Z"
    - latency: 2.377698ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:13:09Z"
    - latency: 2.17716ms
      message: 'network-check-target-ip-10-0-129-177: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:12:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:57:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-ip-10-0-138-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: e7ed4025-95cd-4aa0-83a3-1ce3ede5f08d
    resourceVersion: "52719"
    uid: ef2ce77a-87b7-4198-8a42-bea73be858a3
  spec:
    sourcePod: network-check-source-7d88cb55d8-lgmfj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:04:09Z"
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.268245ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:09Z"
    - latency: 2.263079ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:20:09Z"
    - latency: 1.999975ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:19:09Z"
    - latency: 2.338422ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:18:09Z"
    - latency: 2.207374ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:17:09Z"
    - latency: 2.122156ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:16:09Z"
    - latency: 2.196281ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:15:09Z"
    - latency: 2.290482ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:14:09Z"
    - latency: 2.455263ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:13:09Z"
    - latency: 2.110524ms
      message: 'network-check-target-ip-10-0-138-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:12:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:57:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-ip-10-0-141-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: e7ed4025-95cd-4aa0-83a3-1ce3ede5f08d
    resourceVersion: "52717"
    uid: c6ea381c-df3a-4c75-a704-cec1fb63411e
  spec:
    sourcePod: network-check-source-7d88cb55d8-lgmfj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:04:09Z"
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.38663ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:09Z"
    - latency: 1.319966ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:20:09Z"
    - latency: 1.221068ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:19:09Z"
    - latency: 1.162697ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:18:09Z"
    - latency: 1.131565ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:17:09Z"
    - latency: 867.441µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:16:09Z"
    - latency: 901.139µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:15:09Z"
    - latency: 883.232µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:14:09Z"
    - latency: 1.34738ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:13:09Z"
    - latency: 833.192µs
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:12:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:57:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-7.ec2.internal
      uid: e7ed4025-95cd-4aa0-83a3-1ce3ede5f08d
    resourceVersion: "55752"
    uid: e831ff2a-0c20-4f65-957a-f132c8dc8f3a
  spec:
    sourcePod: network-check-source-7d88cb55d8-lgmfj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:03:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:27:09Z"
    - latency: 1.859313ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:27:09Z"
    - latency: 922.519µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:09Z"
    - latency: 1.553613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:26:09Z"
    - latency: 962.219µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:09Z"
    - latency: 2.303096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:25:09Z"
    - latency: 808.908µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:09Z"
    - latency: 1.667057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:24:09Z"
    - latency: 915.373µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:09Z"
    - latency: 1.745039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:23:09Z"
kind: List
metadata:
  resourceVersion: ""