apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: 2d5bb4f4-79b4-4e9c-8053-3db9fb2736b5
    resourceVersion: "99129"
    uid: 02329d70-cdc4-4c41-a589-4ca98c64e99b
  spec:
    sourcePod: network-check-source-7d88cb55d8-qs6hm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33: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.026756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:04:20Z"
    - latency: 947.544µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:03:20Z"
    - latency: 928.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 950.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 978.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 954.553µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 905.397µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:58:20Z"
    - latency: 1.392779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:57:20Z"
    - latency: 1.078695ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:56:20Z"
    - latency: 1.268422ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: 2d5bb4f4-79b4-4e9c-8053-3db9fb2736b5
    resourceVersion: "97903"
    uid: 6864b045-dcb0-4a6a-afac-b014399deeba
  spec:
    sourcePod: network-check-source-7d88cb55d8-qs6hm
    targetEndpoint: ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:20Z"
      message: 'load-balancer-api-external: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.912524ms
      message: 'load-balancer-api-external: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 8.255127ms
      message: 'load-balancer-api-external: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 5.014048ms
      message: 'load-balancer-api-external: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 9.515228ms
      message: 'load-balancer-api-external: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 5.460073ms
      message: 'load-balancer-api-external: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 7.631813ms
      message: 'load-balancer-api-external: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 5.2479ms
      message: 'load-balancer-api-external: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 8.313861ms
      message: 'load-balancer-api-external: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 5.114133ms
      message: 'load-balancer-api-external: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:58:20Z"
    - latency: 8.713971ms
      message: 'load-balancer-api-external: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: 2d5bb4f4-79b4-4e9c-8053-3db9fb2736b5
    resourceVersion: "97904"
    uid: 87c12ece-f10e-4f1a-8e78-e971dfd3cb6c
  spec:
    sourcePod: network-check-source-7d88cb55d8-qs6hm
    targetEndpoint: ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:20Z"
      message: 'load-balancer-api-internal: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.216327ms
      message: 'load-balancer-api-internal: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 8.215008ms
      message: 'load-balancer-api-internal: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 4.903902ms
      message: 'load-balancer-api-internal: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 9.482134ms
      message: 'load-balancer-api-internal: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 5.488946ms
      message: 'load-balancer-api-internal: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 7.575029ms
      message: 'load-balancer-api-internal: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 5.257977ms
      message: 'load-balancer-api-internal: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 8.24418ms
      message: 'load-balancer-api-internal: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 5.095617ms
      message: 'load-balancer-api-internal: tcp connection to ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:58:20Z"
    - latency: 8.677281ms
      message: 'load-balancer-api-internal: resolved host name ad13b180d2555444a88e0c68148704cd-01ec408b3e1c96fe.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-ip-10-0-131-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: 2d5bb4f4-79b4-4e9c-8053-3db9fb2736b5
    resourceVersion: "99126"
    uid: bf24019e-6fe0-4d85-91d9-ce9de3d741ee
  spec:
    sourcePod: network-check-source-7d88cb55d8-qs6hm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:20Z"
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.276822ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:04:20Z"
    - latency: 931.252µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:03:20Z"
    - latency: 1.49035ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 912.768µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 1.091406ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 902.638µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 1.274431ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:58:20Z"
    - latency: 1.028172ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:57:20Z"
    - latency: 878.529µs
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:56:20Z"
    - latency: 1.224831ms
      message: 'network-check-target-ip-10-0-131-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-ip-10-0-133-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: 2d5bb4f4-79b4-4e9c-8053-3db9fb2736b5
    resourceVersion: "99127"
    uid: 92fc494a-f319-40be-b3b4-3e5f8a3d39b9
  spec:
    sourcePod: network-check-source-7d88cb55d8-qs6hm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:20Z"
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.276979ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:04:20Z"
    - latency: 2.472087ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:03:20Z"
    - latency: 2.401218ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 2.279901ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 2.29072ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 2.13086ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 2.018654ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:58:20Z"
    - latency: 2.27634ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:57:20Z"
    - latency: 2.379807ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:56:20Z"
    - latency: 2.599892ms
      message: 'network-check-target-ip-10-0-133-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-ip-10-0-135-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: 2d5bb4f4-79b4-4e9c-8053-3db9fb2736b5
    resourceVersion: "99125"
    uid: 3f28b78c-0556-494c-b2eb-d8788e127063
  spec:
    sourcePod: network-check-source-7d88cb55d8-qs6hm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:33:20Z"
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.179681ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:04:20Z"
    - latency: 2.008264ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:03:20Z"
    - latency: 2.165085ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 1.974472ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 2.210693ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 2.03413ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 1.875527ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:58:20Z"
    - latency: 2.159614ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:57:20Z"
    - latency: 2.91558ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:56:20Z"
    - latency: 2.684205ms
      message: 'network-check-target-ip-10-0-135-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:26:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-29-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-29.ec2.internal
      uid: 2d5bb4f4-79b4-4e9c-8053-3db9fb2736b5
    resourceVersion: "97901"
    uid: 4ce861ca-faae-4c52-9fef-94d284985499
  spec:
    sourcePod: network-check-source-7d88cb55d8-qs6hm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:32:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.136358ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 1.817403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:02:20Z"
    - latency: 902.304µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 1.566062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:01:20Z"
    - latency: 934.85µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 1.678595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T19:00:20Z"
    - latency: 832.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 1.753248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:59:20Z"
    - latency: 891.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:58:20Z"
    - latency: 1.679343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:58:20Z"
kind: List
metadata:
  resourceVersion: ""