apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: b33aefc6-0fe5-4f82-85c5-5f883a2622fb
    resourceVersion: "32230"
    uid: 65a8b0bd-5b43-4b7d-9e0b-00ce210aad0b
  spec:
    sourcePod: network-check-source-6947749cfc-s7hkv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:41:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.135475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:48:46Z"
    - latency: 1.07112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:47:46Z"
    - latency: 914.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 1.290086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 927.87µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 1.354018ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 1.072135ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:42:46Z"
    - latency: 2.511068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:41:46Z"
    - latency: 1.050362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:40:46Z"
    - latency: 1.053657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: b33aefc6-0fe5-4f82-85c5-5f883a2622fb
    resourceVersion: "30316"
    uid: 30b3987c-0a87-4b51-bb36-8b066adc2e15
  spec:
    sourcePod: network-check-source-6947749cfc-s7hkv
    targetEndpoint: af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:40:46Z"
      message: 'load-balancer-api-external: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.106617ms
      message: 'load-balancer-api-external: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 8.97038ms
      message: 'load-balancer-api-external: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 4.223255ms
      message: 'load-balancer-api-external: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 7.465467ms
      message: 'load-balancer-api-external: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 4.667557ms
      message: 'load-balancer-api-external: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 8.640507ms
      message: 'load-balancer-api-external: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 3.596241ms
      message: 'load-balancer-api-external: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 8.007629ms
      message: 'load-balancer-api-external: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 4.602203ms
      message: 'load-balancer-api-external: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:42:46Z"
    - latency: 8.854124ms
      message: 'load-balancer-api-external: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:42:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: b33aefc6-0fe5-4f82-85c5-5f883a2622fb
    resourceVersion: "30317"
    uid: c22c3d0e-d002-4dd9-8503-bdf32d524ccf
  spec:
    sourcePod: network-check-source-6947749cfc-s7hkv
    targetEndpoint: af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:40:46Z"
      message: 'load-balancer-api-internal: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.091552ms
      message: 'load-balancer-api-internal: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 8.986125ms
      message: 'load-balancer-api-internal: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 4.21823ms
      message: 'load-balancer-api-internal: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 7.510614ms
      message: 'load-balancer-api-internal: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 4.592543ms
      message: 'load-balancer-api-internal: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 8.690078ms
      message: 'load-balancer-api-internal: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 3.583161ms
      message: 'load-balancer-api-internal: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 8.077354ms
      message: 'load-balancer-api-internal: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 4.613024ms
      message: 'load-balancer-api-internal: tcp connection to af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:42:46Z"
    - latency: 8.899997ms
      message: 'load-balancer-api-internal: resolved host name af40c3b07759045cb9c560c5d70bf41e-95163069d94910f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:42:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-ip-10-0-130-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: b33aefc6-0fe5-4f82-85c5-5f883a2622fb
    resourceVersion: "32229"
    uid: c71f6467-d9cb-4902-bc82-d4a5a842f92b
  spec:
    sourcePod: network-check-source-6947749cfc-s7hkv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:41:46Z"
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.540488ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:48:46Z"
    - latency: 2.243831ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:47:46Z"
    - latency: 2.30198ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 2.426509ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 1.816466ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 2.372977ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 2.358368ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:42:46Z"
    - latency: 2.751759ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:41:46Z"
    - latency: 2.260306ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:40:46Z"
    - latency: 2.177595ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-ip-10-0-140-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: b33aefc6-0fe5-4f82-85c5-5f883a2622fb
    resourceVersion: "32227"
    uid: 65da9270-1e73-4044-a6cc-b5ea1c7e2f79
  spec:
    sourcePod: network-check-source-6947749cfc-s7hkv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:41:46Z"
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 859.799µs
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:48:46Z"
    - latency: 938.179µs
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:47:46Z"
    - latency: 1.647275ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 928.579µs
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 943.772µs
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 1.54809ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 901.707µs
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:42:46Z"
    - latency: 1.800084ms
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:41:46Z"
    - latency: 851.82µs
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:40:46Z"
    - latency: 784.613µs
      message: 'network-check-target-ip-10-0-140-24: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-ip-10-0-143-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: b33aefc6-0fe5-4f82-85c5-5f883a2622fb
    resourceVersion: "32228"
    uid: 0770677e-d896-4045-a46c-ae39f374b30f
  spec:
    sourcePod: network-check-source-6947749cfc-s7hkv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:41:46Z"
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.519105ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:48:46Z"
    - latency: 2.171601ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:47:46Z"
    - latency: 2.234021ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 1.792539ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 2.197267ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 2.190482ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 2.238052ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:42:46Z"
    - latency: 2.162627ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:41:46Z"
    - latency: 2.329747ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:40:46Z"
    - latency: 1.99805ms
      message: 'network-check-target-ip-10-0-143-51: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:39:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T02:34:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: b33aefc6-0fe5-4f82-85c5-5f883a2622fb
    resourceVersion: "30315"
    uid: 856b3d9a-37de-4757-a983-61175e4c96d4
  spec:
    sourcePod: network-check-source-6947749cfc-s7hkv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T02:40:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 2.291096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:46:46Z"
    - latency: 856.975µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 1.821885ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:45:46Z"
    - latency: 1.027253ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 1.785595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:44:46Z"
    - latency: 889.756µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 1.692124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:43:46Z"
    - latency: 1.245786ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T02:42:46Z"
    - latency: 1.699863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T02:42:46Z"
kind: List
metadata:
  resourceVersion: ""