apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-81-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-81.ec2.internal
      uid: 3080886c-aacf-467f-a8c5-6a5c6d79b69f
    resourceVersion: "68725"
    uid: 1e457b92-ab91-4f6d-a02d-10aa8b869491
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xzfmt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:58:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.252852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:49Z"
    - latency: 1.272673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 1.260666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 1.21477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 1.277713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 1.45781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:49Z"
    - latency: 1.509669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:49Z"
    - latency: 943.482µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:49Z"
    - latency: 894.032µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:49Z"
    - latency: 1.303108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-81-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-81.ec2.internal
      uid: 3080886c-aacf-467f-a8c5-6a5c6d79b69f
    resourceVersion: "67730"
    uid: b262a4fc-bea6-46e5-afaf-447e63febe50
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xzfmt
    targetEndpoint: a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:57:49Z"
      message: 'load-balancer-api-external: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.946583ms
      message: 'load-balancer-api-external: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 8.823726ms
      message: 'load-balancer-api-external: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 4.247136ms
      message: 'load-balancer-api-external: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 8.128323ms
      message: 'load-balancer-api-external: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 4.270329ms
      message: 'load-balancer-api-external: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 8.766873ms
      message: 'load-balancer-api-external: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 4.348398ms
      message: 'load-balancer-api-external: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 10.19249ms
      message: 'load-balancer-api-external: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 5.269988ms
      message: 'load-balancer-api-external: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:49Z"
    - latency: 10.090487ms
      message: 'load-balancer-api-external: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:35:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-81-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-81.ec2.internal
      uid: 3080886c-aacf-467f-a8c5-6a5c6d79b69f
    resourceVersion: "67731"
    uid: 33b84702-59e5-4aa1-a62f-0dc0ea8c01af
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xzfmt
    targetEndpoint: a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:57:49Z"
      message: 'load-balancer-api-internal: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.975675ms
      message: 'load-balancer-api-internal: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 8.812984ms
      message: 'load-balancer-api-internal: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 4.267291ms
      message: 'load-balancer-api-internal: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 8.118705ms
      message: 'load-balancer-api-internal: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 4.367383ms
      message: 'load-balancer-api-internal: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 8.826233ms
      message: 'load-balancer-api-internal: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 5.516114ms
      message: 'load-balancer-api-internal: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 10.227809ms
      message: 'load-balancer-api-internal: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 5.261439ms
      message: 'load-balancer-api-internal: tcp connection to a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:49Z"
    - latency: 10.124022ms
      message: 'load-balancer-api-internal: resolved host name a1e52d22434954aa683edadc827eceb7-5a77e530cb420eab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:35:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-81-to-network-check-target-ip-10-0-128-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-81.ec2.internal
      uid: 3080886c-aacf-467f-a8c5-6a5c6d79b69f
    resourceVersion: "68722"
    uid: db958b87-5e22-4efc-a919-3de876ade9e4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xzfmt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:58:49Z"
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.128933ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:49Z"
    - latency: 2.180257ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 2.272084ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 2.175955ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 2.642274ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 2.052457ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:49Z"
    - latency: 2.341589ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:49Z"
    - latency: 2.12002ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:49Z"
    - latency: 2.280864ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:49Z"
    - latency: 3.563752ms
      message: 'network-check-target-ip-10-0-128-255: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-81-to-network-check-target-ip-10-0-140-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-81.ec2.internal
      uid: 3080886c-aacf-467f-a8c5-6a5c6d79b69f
    resourceVersion: "68723"
    uid: 64c89289-4862-48b5-b080-b3cb03a1dd9a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xzfmt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:58:49Z"
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.187µs
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:49Z"
    - latency: 1.054637ms
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 1.207169ms
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 993.027µs
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 1.072389ms
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 1.084283ms
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:49Z"
    - latency: 1.136008ms
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:49Z"
    - latency: 931.582µs
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:49Z"
    - latency: 1.031543ms
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:49Z"
    - latency: 1.703985ms
      message: 'network-check-target-ip-10-0-140-81: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-81-to-network-check-target-ip-10-0-143-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-81.ec2.internal
      uid: 3080886c-aacf-467f-a8c5-6a5c6d79b69f
    resourceVersion: "68724"
    uid: acef221f-3f7a-44a8-9efd-9187cde67b36
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xzfmt
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:58:49Z"
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.26086ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:40:49Z"
    - latency: 2.450952ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 2.153752ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 2.422389ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 2.587211ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 2.606638ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:49Z"
    - latency: 2.388359ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:34:49Z"
    - latency: 2.191296ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:33:49Z"
    - latency: 1.952741ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:32:49Z"
    - latency: 3.586431ms
      message: 'network-check-target-ip-10-0-143-124: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:31:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T21:51:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-81-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-81.ec2.internal
      uid: 3080886c-aacf-467f-a8c5-6a5c6d79b69f
    resourceVersion: "67729"
    uid: ff59d484-b175-460e-92b7-cf9320db2ea8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xzfmt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T21:57:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.323µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 1.825051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:39:49Z"
    - latency: 967.448µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 1.76787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:38:49Z"
    - latency: 974.026µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 2.014374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:37:49Z"
    - latency: 957.616µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 1.828837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:36:49Z"
    - latency: 905.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:35:49Z"
    - latency: 2.45963ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:35:49Z"
kind: List
metadata:
  resourceVersion: ""