apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:38:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 68fa4311-0b7b-405d-9b7e-e0aff066746c
    resourceVersion: "30292"
    uid: 6f099095-fb1b-4b6e-aebd-46a2c0ff5dea
  spec:
    sourcePod: network-check-source-56d84b9f44-qdwsx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:45:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.089383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:52:29Z"
    - latency: 1.178191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:51:29Z"
    - latency: 1.157439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 847.575µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 856.3µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 872.377µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 1.026134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:46:29Z"
    - latency: 1.391123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:45:29Z"
    - latency: 1.29851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:44:29Z"
    - latency: 1.095028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:43:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:38:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 68fa4311-0b7b-405d-9b7e-e0aff066746c
    resourceVersion: "28759"
    uid: 8bbf3651-4ed7-43cc-93d1-bd4a7d5ed9c7
  spec:
    sourcePod: network-check-source-56d84b9f44-qdwsx
    targetEndpoint: a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:44:29Z"
      message: 'load-balancer-api-external: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.475047ms
      message: 'load-balancer-api-external: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 6.615807ms
      message: 'load-balancer-api-external: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 4.375008ms
      message: 'load-balancer-api-external: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 6.08816ms
      message: 'load-balancer-api-external: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 5.172959ms
      message: 'load-balancer-api-external: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 7.168636ms
      message: 'load-balancer-api-external: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 4.554778ms
      message: 'load-balancer-api-external: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 6.762488ms
      message: 'load-balancer-api-external: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 5.510003ms
      message: 'load-balancer-api-external: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:46:29Z"
    - latency: 7.050143ms
      message: 'load-balancer-api-external: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:46:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:38:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 68fa4311-0b7b-405d-9b7e-e0aff066746c
    resourceVersion: "28760"
    uid: ebf13eac-ccd8-45ae-8e9d-6694a93ecd59
  spec:
    sourcePod: network-check-source-56d84b9f44-qdwsx
    targetEndpoint: a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:44:29Z"
      message: 'load-balancer-api-internal: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.654727ms
      message: 'load-balancer-api-internal: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 6.57049ms
      message: 'load-balancer-api-internal: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 4.397615ms
      message: 'load-balancer-api-internal: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 6.111854ms
      message: 'load-balancer-api-internal: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 5.163721ms
      message: 'load-balancer-api-internal: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 7.112572ms
      message: 'load-balancer-api-internal: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 4.603666ms
      message: 'load-balancer-api-internal: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 6.715637ms
      message: 'load-balancer-api-internal: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 5.539164ms
      message: 'load-balancer-api-internal: tcp connection to a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:46:29Z"
    - latency: 7.029227ms
      message: 'load-balancer-api-internal: resolved host name a252956559d294c8aad0820b9dde4c7f-93b447b5118412af.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:46:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:38:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-ip-10-0-135-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 68fa4311-0b7b-405d-9b7e-e0aff066746c
    resourceVersion: "30290"
    uid: 316f1395-ed92-415c-a42c-b039efc70956
  spec:
    sourcePod: network-check-source-56d84b9f44-qdwsx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:45:29Z"
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.071491ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:52:29Z"
    - latency: 1.954933ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:51:29Z"
    - latency: 2.243754ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 2.214765ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 2.219249ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 1.930073ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 1.953646ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:46:29Z"
    - latency: 2.440673ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:45:29Z"
    - latency: 2.400081ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:44:29Z"
    - latency: 2.412055ms
      message: 'network-check-target-ip-10-0-135-67: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:43:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:38:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-ip-10-0-140-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 68fa4311-0b7b-405d-9b7e-e0aff066746c
    resourceVersion: "30291"
    uid: d9f75de9-8c09-422a-939c-9dd8ca6e0edc
  spec:
    sourcePod: network-check-source-56d84b9f44-qdwsx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:45:29Z"
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.084888ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:52:29Z"
    - latency: 2.141509ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:51:29Z"
    - latency: 2.187615ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 2.232152ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 2.14862ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 2.156322ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 2.200992ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:46:29Z"
    - latency: 2.23735ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:45:29Z"
    - latency: 2.425076ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:44:29Z"
    - latency: 2.386545ms
      message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:43:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:38:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-ip-10-0-142-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 68fa4311-0b7b-405d-9b7e-e0aff066746c
    resourceVersion: "30289"
    uid: cced7cf1-b1ba-4219-adfe-eeb3bcb68be7
  spec:
    sourcePod: network-check-source-56d84b9f44-qdwsx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:45:29Z"
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 765.905µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:52:29Z"
    - latency: 1.350021ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:51:29Z"
    - latency: 928.843µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 850.782µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 838.762µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 807.48µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 669.927µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:46:29Z"
    - latency: 940.458µs
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:45:29Z"
    - latency: 1.832629ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:44:29Z"
    - latency: 1.204427ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:43:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T16:38:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-172.ec2.internal
      uid: 68fa4311-0b7b-405d-9b7e-e0aff066746c
    resourceVersion: "28757"
    uid: f61960a3-fe20-44f2-a689-bfefb78bb966
  spec:
    sourcePod: network-check-source-56d84b9f44-qdwsx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T16:44:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.345µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 1.724482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:50:29Z"
    - latency: 888.549µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 1.605392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:49:29Z"
    - latency: 1.030948ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 1.744325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:48:29Z"
    - latency: 1.092861ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 1.744534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:47:29Z"
    - latency: 906.663µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T16:46:29Z"
    - latency: 2.004497ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T16:46:29Z"
kind: List
metadata:
  resourceVersion: ""