apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-205-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-205.ec2.internal
      uid: 66647de7-a320-49e4-9a3e-356775c73e72
    resourceVersion: "16312"
    uid: 4d04ce2f-ea3c-445b-82fd-c5253900726b
  spec:
    sourcePod: network-check-source-869dcfcdcd-vc9ss
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.690659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:42Z"
    - latency: 953.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:42Z"
    - latency: 1.280099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 1.041949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 864.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 982.112µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 1.46484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:42Z"
    - latency: 1.026919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:42Z"
    - latency: 1.053354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:42Z"
    - latency: 1.114919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-205-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-205.ec2.internal
      uid: 66647de7-a320-49e4-9a3e-356775c73e72
    resourceVersion: "15574"
    uid: f0208fcb-9544-402d-b038-91260cf48a75
  spec:
    sourcePod: network-check-source-869dcfcdcd-vc9ss
    targetEndpoint: adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:42Z"
      message: 'load-balancer-api-external: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.660047ms
      message: 'load-balancer-api-external: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 9.590421ms
      message: 'load-balancer-api-external: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 4.292436ms
      message: 'load-balancer-api-external: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 8.159353ms
      message: 'load-balancer-api-external: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 6.316083ms
      message: 'load-balancer-api-external: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 8.539447ms
      message: 'load-balancer-api-external: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 4.17983ms
      message: 'load-balancer-api-external: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 7.745838ms
      message: 'load-balancer-api-external: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 5.101725ms
      message: 'load-balancer-api-external: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:42Z"
    - latency: 10.517949ms
      message: 'load-balancer-api-external: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:03:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-205-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-205.ec2.internal
      uid: 66647de7-a320-49e4-9a3e-356775c73e72
    resourceVersion: "15575"
    uid: 8faf3781-9e9a-4b35-8f34-973e0f262909
  spec:
    sourcePod: network-check-source-869dcfcdcd-vc9ss
    targetEndpoint: adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:42Z"
      message: 'load-balancer-api-internal: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.355196ms
      message: 'load-balancer-api-internal: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 9.603501ms
      message: 'load-balancer-api-internal: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 10.715362ms
      message: 'load-balancer-api-internal: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 8.190201ms
      message: 'load-balancer-api-internal: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 4.507229ms
      message: 'load-balancer-api-internal: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 8.467544ms
      message: 'load-balancer-api-internal: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 3.583241ms
      message: 'load-balancer-api-internal: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 7.729911ms
      message: 'load-balancer-api-internal: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 5.555622ms
      message: 'load-balancer-api-internal: tcp connection to adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:42Z"
    - latency: 10.47834ms
      message: 'load-balancer-api-internal: resolved host name adfe23a9cad4548a98f766745076651d-79b5a374eb85f2a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:03:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-205-to-network-check-target-ip-10-0-136-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-205.ec2.internal
      uid: 66647de7-a320-49e4-9a3e-356775c73e72
    resourceVersion: "16309"
    uid: b844de4a-00b9-4443-8556-ae493533c949
  spec:
    sourcePod: network-check-source-869dcfcdcd-vc9ss
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:42Z"
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.055992ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:42Z"
    - latency: 2.540018ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:42Z"
    - latency: 2.539377ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 2.462581ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 2.09706ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 2.31126ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 2.15825ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:42Z"
    - latency: 2.427433ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:42Z"
    - latency: 2.251317ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:42Z"
    - latency: 2.125984ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-205-to-network-check-target-ip-10-0-136-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-205.ec2.internal
      uid: 66647de7-a320-49e4-9a3e-356775c73e72
    resourceVersion: "16310"
    uid: 18bba4d1-023b-45ec-b70d-99b303374131
  spec:
    sourcePod: network-check-source-869dcfcdcd-vc9ss
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:42Z"
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.546338ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:42Z"
    - latency: 2.490514ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:42Z"
    - latency: 2.447837ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 2.890513ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 2.528803ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 2.443166ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 2.51572ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:42Z"
    - latency: 2.478998ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:42Z"
    - latency: 2.476067ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:42Z"
    - latency: 2.435617ms
      message: 'network-check-target-ip-10-0-136-73: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-205-to-network-check-target-ip-10-0-142-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-205.ec2.internal
      uid: 66647de7-a320-49e4-9a3e-356775c73e72
    resourceVersion: "16311"
    uid: ea0ec04c-8bd1-4324-a153-6b2645bdc999
  spec:
    sourcePod: network-check-source-869dcfcdcd-vc9ss
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:02:42Z"
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.780189ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:09:42Z"
    - latency: 1.054602ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:08:42Z"
    - latency: 788.995µs
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 1.033818ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 902.423µs
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 890.258µs
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 962.667µs
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:42Z"
    - latency: 860.213µs
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:02:42Z"
    - latency: 947.752µs
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:01:42Z"
    - latency: 1.31995ms
      message: 'network-check-target-ip-10-0-142-205: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:00:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T16:55:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-205-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-205.ec2.internal
      uid: 66647de7-a320-49e4-9a3e-356775c73e72
    resourceVersion: "15573"
    uid: 3b4b33cd-10fc-42e3-bc53-4f86e6d9f2d2
  spec:
    sourcePod: network-check-source-869dcfcdcd-vc9ss
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:01:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.224µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 1.655978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:07:42Z"
    - latency: 1.213546ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 1.66985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:06:42Z"
    - latency: 810.087µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 1.907243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:05:42Z"
    - latency: 846.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 1.72986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:04:42Z"
    - latency: 1.062354ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:03:42Z"
    - latency: 1.875381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:03:42Z"
kind: List
metadata:
  resourceVersion: ""