apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T11:31:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-173-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-173.ec2.internal
      uid: 2c03695b-fc1a-4267-89fc-528bf7f23821
    resourceVersion: "53761"
    uid: 37a3e367-a6cf-4435-877a-a6ca6ec52795
  spec:
    sourcePod: network-check-source-989f8b8dc-t4dxm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T11:38:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 773.005µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 898.71µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 933.608µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 872.264µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:03:55Z"
    - latency: 935.847µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:02:55Z"
    - latency: 1.114282ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:01:55Z"
    - latency: 833.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:00:55Z"
    - latency: 822.32µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:59:55Z"
    - latency: 739.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:58:55Z"
    - latency: 836.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T11:31:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-173-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-173.ec2.internal
      uid: 2c03695b-fc1a-4267-89fc-528bf7f23821
    resourceVersion: "54741"
    uid: df6c5eb3-cc14-4304-b974-e1bbc0df21b7
  spec:
    sourcePod: network-check-source-989f8b8dc-t4dxm
    targetEndpoint: a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T11:37:55Z"
      message: 'load-balancer-api-external: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.13905ms
      message: 'load-balancer-api-external: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:07:55Z"
    - latency: 8.367111ms
      message: 'load-balancer-api-external: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:07:55Z"
    - latency: 4.68138ms
      message: 'load-balancer-api-external: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 8.199821ms
      message: 'load-balancer-api-external: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 5.052283ms
      message: 'load-balancer-api-external: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 7.74495ms
      message: 'load-balancer-api-external: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 4.975098ms
      message: 'load-balancer-api-external: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 8.238666ms
      message: 'load-balancer-api-external: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 5.446899ms
      message: 'load-balancer-api-external: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:03:55Z"
    - latency: 8.829056ms
      message: 'load-balancer-api-external: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:03:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T11:31:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-173-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-173.ec2.internal
      uid: 2c03695b-fc1a-4267-89fc-528bf7f23821
    resourceVersion: "54740"
    uid: 94eda260-39fa-45e4-8d65-2c1092c19255
  spec:
    sourcePod: network-check-source-989f8b8dc-t4dxm
    targetEndpoint: a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T11:37:55Z"
      message: 'load-balancer-api-internal: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.138668ms
      message: 'load-balancer-api-internal: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:07:55Z"
    - latency: 8.433846ms
      message: 'load-balancer-api-internal: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:07:55Z"
    - latency: 4.673286ms
      message: 'load-balancer-api-internal: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 8.252066ms
      message: 'load-balancer-api-internal: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 5.031471ms
      message: 'load-balancer-api-internal: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 7.793142ms
      message: 'load-balancer-api-internal: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 5.843928ms
      message: 'load-balancer-api-internal: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 8.149786ms
      message: 'load-balancer-api-internal: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 3.857724ms
      message: 'load-balancer-api-internal: tcp connection to a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:03:55Z"
    - latency: 8.911138ms
      message: 'load-balancer-api-internal: resolved host name a82e1fe501e3f4d53b9fc8c9d1f1d78d-477d70e211e7bd17.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:03:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T11:31:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-173-to-network-check-target-ip-10-0-131-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-173.ec2.internal
      uid: 2c03695b-fc1a-4267-89fc-528bf7f23821
    resourceVersion: "53760"
    uid: f585a2ee-0fcb-4978-b2e5-07ed0c87575a
  spec:
    sourcePod: network-check-source-989f8b8dc-t4dxm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T11:38:55Z"
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.366614ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 2.393852ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 2.117761ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 2.139882ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:03:55Z"
    - latency: 2.266889ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:02:55Z"
    - latency: 2.39715ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:01:55Z"
    - latency: 2.203736ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:00:55Z"
    - latency: 2.312292ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:59:55Z"
    - latency: 2.129732ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:58:55Z"
    - latency: 1.752079ms
      message: 'network-check-target-ip-10-0-131-176: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T11:31:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-173-to-network-check-target-ip-10-0-138-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-173.ec2.internal
      uid: 2c03695b-fc1a-4267-89fc-528bf7f23821
    resourceVersion: "53759"
    uid: 01833000-3784-4807-b671-31ce87150523
  spec:
    sourcePod: network-check-source-989f8b8dc-t4dxm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T11:38:55Z"
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.043479ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 1.925796ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 1.767389ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 1.799435ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:03:55Z"
    - latency: 1.686088ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:02:55Z"
    - latency: 1.89226ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:01:55Z"
    - latency: 1.658318ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:00:55Z"
    - latency: 1.909174ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:59:55Z"
    - latency: 1.519394ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:58:55Z"
    - latency: 1.755236ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T11:31:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-173-to-network-check-target-ip-10-0-143-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-173.ec2.internal
      uid: 2c03695b-fc1a-4267-89fc-528bf7f23821
    resourceVersion: "53758"
    uid: 64d9c2e5-c6e4-4553-94f6-5c7acb05c885
  spec:
    sourcePod: network-check-source-989f8b8dc-t4dxm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T11:38:55Z"
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.001554ms
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 901.677µs
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 731.617µs
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 1.107763ms
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:03:55Z"
    - latency: 882.297µs
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:02:55Z"
    - latency: 800.703µs
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:01:55Z"
    - latency: 918.437µs
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:00:55Z"
    - latency: 998.476µs
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:59:55Z"
    - latency: 1.294112ms
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:58:55Z"
    - latency: 1.247951ms
      message: 'network-check-target-ip-10-0-143-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T11:57:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T11:31:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-173-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-173.ec2.internal
      uid: 2c03695b-fc1a-4267-89fc-528bf7f23821
    resourceVersion: "54738"
    uid: acc362dc-2265-4d67-bead-835fd1eb55af
  spec:
    sourcePod: network-check-source-989f8b8dc-t4dxm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T11:37:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.568µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:07:55Z"
    - latency: 1.918514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:07:55Z"
    - latency: 1.200143ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 1.427861ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:06:55Z"
    - latency: 910.271µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 1.924783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:05:55Z"
    - latency: 879.575µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 1.638725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:04:55Z"
    - latency: 977.405µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:03:55Z"
    - latency: 1.954944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:03:55Z"
kind: List
metadata:
  resourceVersion: ""