apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-213-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-213.ec2.internal
      uid: 0a7be1dd-dc44-4e58-ad49-e5f42b58acd8
    resourceVersion: "55084"
    uid: 8ff4bb89-fe51-4198-a217-f46f843322fc
  spec:
    sourcePod: network-check-source-989f8b8dc-4hlhm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.130287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 901.454µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 1.113989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 1.232719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:20Z"
    - latency: 1.066896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:20Z"
    - latency: 1.008174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:20Z"
    - latency: 1.693575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:20Z"
    - latency: 996.892µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:20Z"
    - latency: 1.053553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:20Z"
    - latency: 1.170721ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-213-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-213.ec2.internal
      uid: 0a7be1dd-dc44-4e58-ad49-e5f42b58acd8
    resourceVersion: "56146"
    uid: 217edf34-bc7a-4a1e-bb68-4082d7f09b98
  spec:
    sourcePod: network-check-source-989f8b8dc-4hlhm
    targetEndpoint: a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:33:20Z"
      message: 'load-balancer-api-external: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.576479ms
      message: 'load-balancer-api-external: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:20Z"
    - latency: 8.669636ms
      message: 'load-balancer-api-external: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:03:20Z"
    - latency: 5.098635ms
      message: 'load-balancer-api-external: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 9.286478ms
      message: 'load-balancer-api-external: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 6.286784ms
      message: 'load-balancer-api-external: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 13.173521ms
      message: 'load-balancer-api-external: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 5.501215ms
      message: 'load-balancer-api-external: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 7.924744ms
      message: 'load-balancer-api-external: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 3.826543ms
      message: 'load-balancer-api-external: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:20Z"
    - latency: 9.930375ms
      message: 'load-balancer-api-external: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-213-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-213.ec2.internal
      uid: 0a7be1dd-dc44-4e58-ad49-e5f42b58acd8
    resourceVersion: "56145"
    uid: bd8de45f-0cc5-4525-a5bf-2f9e393f8bc8
  spec:
    sourcePod: network-check-source-989f8b8dc-4hlhm
    targetEndpoint: a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:33:20Z"
      message: 'load-balancer-api-internal: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.493735ms
      message: 'load-balancer-api-internal: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:20Z"
    - latency: 8.747114ms
      message: 'load-balancer-api-internal: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:03:20Z"
    - latency: 5.053615ms
      message: 'load-balancer-api-internal: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 9.312278ms
      message: 'load-balancer-api-internal: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 6.271775ms
      message: 'load-balancer-api-internal: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 13.241615ms
      message: 'load-balancer-api-internal: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 4.195745ms
      message: 'load-balancer-api-internal: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 8.011071ms
      message: 'load-balancer-api-internal: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 4.354363ms
      message: 'load-balancer-api-internal: tcp connection to a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:20Z"
    - latency: 9.988465ms
      message: 'load-balancer-api-internal: resolved host name a255f87dc726c497fbfd927cb259838e-6051dc654a85ed63.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-213-to-network-check-target-ip-10-0-137-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-213.ec2.internal
      uid: 0a7be1dd-dc44-4e58-ad49-e5f42b58acd8
    resourceVersion: "55082"
    uid: 9f3beb8b-bbce-4a09-94ea-2b17bd29312a
  spec:
    sourcePod: network-check-source-989f8b8dc-4hlhm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34:20Z"
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.241268ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 2.163778ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 2.387288ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 2.275407ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:20Z"
    - latency: 2.249468ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:20Z"
    - latency: 2.401393ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:20Z"
    - latency: 2.123097ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:20Z"
    - latency: 2.323969ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:20Z"
    - latency: 2.417112ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:20Z"
    - latency: 2.229612ms
      message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-213-to-network-check-target-ip-10-0-138-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-213.ec2.internal
      uid: 0a7be1dd-dc44-4e58-ad49-e5f42b58acd8
    resourceVersion: "55083"
    uid: 87776a8d-bd41-4829-9c19-c68125210be9
  spec:
    sourcePod: network-check-source-989f8b8dc-4hlhm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34:20Z"
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.869911ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 1.951985ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 2.535559ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 2.667023ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:20Z"
    - latency: 1.952276ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:20Z"
    - latency: 1.893757ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:20Z"
    - latency: 1.920823ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:20Z"
    - latency: 2.613447ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:20Z"
    - latency: 2.549364ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:20Z"
    - latency: 1.889827ms
      message: 'network-check-target-ip-10-0-138-90: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-213-to-network-check-target-ip-10-0-141-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-213.ec2.internal
      uid: 0a7be1dd-dc44-4e58-ad49-e5f42b58acd8
    resourceVersion: "55081"
    uid: 78ed0f28-2e0a-4a01-90b7-a6318885092e
  spec:
    sourcePod: network-check-source-989f8b8dc-4hlhm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:34:20Z"
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.684µs
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 824.7µs
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 1.245573ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 1.630471ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:20Z"
    - latency: 1.14731ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:20Z"
    - latency: 1.581756ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:20Z"
    - latency: 2.151679ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:20Z"
    - latency: 924.514µs
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:20Z"
    - latency: 1.229724ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:20Z"
    - latency: 798.127µs
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:27:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-213-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-213.ec2.internal
      uid: 0a7be1dd-dc44-4e58-ad49-e5f42b58acd8
    resourceVersion: "56144"
    uid: fb80e5a1-a408-4b27-972c-0a9413af43df
  spec:
    sourcePod: network-check-source-989f8b8dc-4hlhm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:33:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.464µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:03:20Z"
    - latency: 1.506308ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:03:20Z"
    - latency: 1.112284ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 1.898096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:02:20Z"
    - latency: 742.586µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 2.03719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:01:20Z"
    - latency: 1.387403ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 1.840262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:00:20Z"
    - latency: 903.012µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:20Z"
    - latency: 1.641761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:20Z"
kind: List
metadata:
  resourceVersion: ""