apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:00:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.us-east-2.compute.internal
      uid: eff51cbc-47df-4f6f-859b-acf207140704
    resourceVersion: "53362"
    uid: 80c809b6-965e-4491-b314-d85cd52acd8a
  spec:
    sourcePod: network-check-source-6f78d59f99-mc2zc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:07:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.038751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:04Z"
    - latency: 1.275668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 1.51994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 843.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 1.115876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 1.084578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:44:04Z"
    - latency: 799.8µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:43:04Z"
    - latency: 1.154231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:42:04Z"
    - latency: 886.425µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:41:04Z"
    - latency: 1.004125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:00:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.us-east-2.compute.internal
      uid: eff51cbc-47df-4f6f-859b-acf207140704
    resourceVersion: "51304"
    uid: 9143801b-a0a3-42a2-8a15-6e71504c1aa1
  spec:
    sourcePod: network-check-source-6f78d59f99-mc2zc
    targetEndpoint: ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:06:04Z"
      message: 'load-balancer-api-external: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.237528ms
      message: 'load-balancer-api-external: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 7.084511ms
      message: 'load-balancer-api-external: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 6.136102ms
      message: 'load-balancer-api-external: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 9.373007ms
      message: 'load-balancer-api-external: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 6.801616ms
      message: 'load-balancer-api-external: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 8.165311ms
      message: 'load-balancer-api-external: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 6.22317ms
      message: 'load-balancer-api-external: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 7.338936ms
      message: 'load-balancer-api-external: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 6.507378ms
      message: 'load-balancer-api-external: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:44:04Z"
    - latency: 7.782914ms
      message: 'load-balancer-api-external: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:44:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:00:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.us-east-2.compute.internal
      uid: eff51cbc-47df-4f6f-859b-acf207140704
    resourceVersion: "51305"
    uid: 7cba436c-8fe9-4145-a0d2-8fa1ccac38c6
  spec:
    sourcePod: network-check-source-6f78d59f99-mc2zc
    targetEndpoint: ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:06:04Z"
      message: 'load-balancer-api-internal: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.230988ms
      message: 'load-balancer-api-internal: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 7.005843ms
      message: 'load-balancer-api-internal: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 6.124078ms
      message: 'load-balancer-api-internal: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 9.405331ms
      message: 'load-balancer-api-internal: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 6.856791ms
      message: 'load-balancer-api-internal: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 8.090623ms
      message: 'load-balancer-api-internal: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 6.709684ms
      message: 'load-balancer-api-internal: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 7.469327ms
      message: 'load-balancer-api-internal: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 6.511609ms
      message: 'load-balancer-api-internal: tcp connection to ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:44:04Z"
    - latency: 7.719445ms
      message: 'load-balancer-api-internal: resolved host name ac74259a4942e4195bd05942d6327537-38aed0da12f1f398.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:44:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:00:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-ip-10-0-129-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.us-east-2.compute.internal
      uid: eff51cbc-47df-4f6f-859b-acf207140704
    resourceVersion: "53361"
    uid: 955d330e-2f9b-449b-9deb-8a6bc681acfc
  spec:
    sourcePod: network-check-source-6f78d59f99-mc2zc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:07:04Z"
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.347388ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:04Z"
    - latency: 2.127345ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 2.985212ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 1.909937ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 2.253656ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 2.596392ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:44:04Z"
    - latency: 2.303398ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:43:04Z"
    - latency: 2.17249ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:42:04Z"
    - latency: 2.040842ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:41:04Z"
    - latency: 2.185158ms
      message: 'network-check-target-ip-10-0-129-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:00:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-ip-10-0-136-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.us-east-2.compute.internal
      uid: eff51cbc-47df-4f6f-859b-acf207140704
    resourceVersion: "53360"
    uid: abf9e850-237f-418b-83dc-b2619f00d66c
  spec:
    sourcePod: network-check-source-6f78d59f99-mc2zc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:07:04Z"
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.287935ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:04Z"
    - latency: 2.244988ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 2.649275ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 1.982058ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 2.190769ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 2.364544ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:44:04Z"
    - latency: 2.142666ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:43:04Z"
    - latency: 2.289134ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:42:04Z"
    - latency: 2.020855ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:41:04Z"
    - latency: 2.271081ms
      message: 'network-check-target-ip-10-0-136-236: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:00:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-ip-10-0-140-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.us-east-2.compute.internal
      uid: eff51cbc-47df-4f6f-859b-acf207140704
    resourceVersion: "53359"
    uid: ea396686-ede3-44a8-b089-7cffab12e7ba
  spec:
    sourcePod: network-check-source-6f78d59f99-mc2zc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:07:04Z"
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.131µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:04Z"
    - latency: 1.447138ms
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 1.142484ms
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 917.913µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 858.632µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 999.779µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:44:04Z"
    - latency: 991.368µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:43:04Z"
    - latency: 1.018803ms
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:42:04Z"
    - latency: 1.309347ms
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:41:04Z"
    - latency: 1.029756ms
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:40:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:00:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.us-east-2.compute.internal
      uid: eff51cbc-47df-4f6f-859b-acf207140704
    resourceVersion: "51302"
    uid: 0d7761fc-f137-454d-9c31-8dff1f7fe301
  spec:
    sourcePod: network-check-source-6f78d59f99-mc2zc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:06:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.209µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 1.852267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:48:04Z"
    - latency: 1.636592ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 3.192787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:47:04Z"
    - latency: 962.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 1.592606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:46:04Z"
    - latency: 1.302341ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 1.768014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:45:04Z"
    - latency: 1.011167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:44:04Z"
    - latency: 1.787077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:44:04Z"
kind: List
metadata:
  resourceVersion: ""