apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 165 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-kubernetes-apiserver-endpoint-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "39871" uid: b56b4d71-ff8a-448f-ab9f-261057989575 spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-12T21:23:37Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.241996ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 2.393119ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:29:37Z" - latency: 12.058343ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:28:37Z" - latency: 3.002402ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:27:37Z" - latency: 2.330656ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:26:37Z" - latency: 2.613063ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:25:37Z" - latency: 7.202474ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:24:37Z" - latency: 4.046299ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:23:37Z" - latency: 2.378958ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:22:37Z" - latency: 828.441µs message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:21:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-kubernetes-apiserver-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "37661" uid: fc80a1f6-7507-4fce-80e6-10b1d65fc369 spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: 172.30.233.56:443 status: conditions: - lastTransitionTime: "2026-03-12T21:23:37Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.879155ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 3.603237ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:29:37Z" - latency: 13.371104ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:28:37Z" - latency: 1.23239ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:27:37Z" - latency: 1.286441ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:26:37Z" - latency: 2.1ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:25:37Z" - latency: 7.069531ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:24:37Z" - latency: 4.260593ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:23:37Z" - latency: 2.074491ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:22:37Z" - latency: 4.53565ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.233.56:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:21:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "37663" uid: 705f1e4a-bb27-4735-ba79-fb5a28cc01a8 spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-12T21:23:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 12.473052ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 2.012278ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:29:37Z" - latency: 13.320553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:28:37Z" - latency: 2.729026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:27:37Z" - latency: 1.463237ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:26:37Z" - latency: 3.585478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:25:37Z" - latency: 8.320862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:24:37Z" - latency: 3.791552ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:23:37Z" - latency: 2.231704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:22:37Z" - latency: 4.236973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:21:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "39690" uid: 2357dcc3-e906-4e70-ab0d-358930032d55 spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-12T21:22:37Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 368.979µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:34:37Z" - latency: 11.336875ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:34:37Z" - latency: 1.161278ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:33:37Z" - latency: 12.596425ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:33:37Z" - latency: 272.546µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:32:37Z" - latency: 7.488061ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:32:37Z" - latency: 322.087µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:31:37Z" - latency: 8.658109ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:31:37Z" - latency: 2.86973ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 14.660824ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:30:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "39691" uid: 476f27da-3cfb-4c69-845a-bd167efa59ce spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-12T21:22:37Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 339.558µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:34:37Z" - latency: 11.209642ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:34:37Z" - latency: 1.368474ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:33:37Z" - latency: 12.488093ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:33:37Z" - latency: 835.521µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:32:37Z" - latency: 6.435385ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:32:37Z" - latency: 863.181µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:31:37Z" - latency: 7.144793ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:31:37Z" - latency: 3.009242ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 13.326673ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-12T21:30:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-network-check-target-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "37660" uid: 8bbfdc9b-9031-4848-a0b4-63688e61f20f spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-12T21:23:37Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.697735ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 1.137238ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:29:37Z" - latency: 12.948564ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:28:37Z" - latency: 3.039134ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:27:37Z" - latency: 1.440295ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:26:37Z" - latency: 5.595494ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:25:37Z" - latency: 12.565484ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:24:37Z" - latency: 8.004485ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:23:37Z" - latency: 5.652037ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:22:37Z" - latency: 9.741706ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:21:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "39689" uid: cc5bcfbe-624c-44f8-bf99-a0a356931e3d spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-12T21:22:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.291176ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:34:37Z" - latency: 3.329951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-12T21:34:37Z" - latency: 1.698431ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:33:37Z" - latency: 5.547634ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-12T21:33:37Z" - latency: 966.683µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:32:37Z" - latency: 3.74867ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-12T21:32:37Z" - latency: 2.028369ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:31:37Z" - latency: 3.145996ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-12T21:31:37Z" - latency: 17.270948ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 3.827192ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-12T21:30:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-openshift-apiserver-endpoint-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "37664" uid: e695b1f6-a030-4a54-99ad-c329c250117b spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: 10.128.0.34:8443 status: conditions: - lastTransitionTime: "2026-03-12T21:23:37Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.172994ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 3.679659ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:29:37Z" - latency: 12.592045ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:28:37Z" - latency: 3.434173ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:27:37Z" - latency: 2.640944ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:26:37Z" - latency: 6.695892ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:25:37Z" - latency: 15.199278ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:24:37Z" - latency: 8.651659ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:23:37Z" - latency: 2.202644ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:22:37Z" - latency: 6.827166ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:21:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-12T21:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-0-to-openshift-apiserver-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-0 uid: 2dfae8b8-e7f5-4d57-9eba-36a0bb1a6e83 resourceVersion: "37665" uid: 907a0a0b-d1af-4109-b93e-e7c1c6f443ea spec: sourcePod: network-check-source-7c67b67d47-bv4x6 targetEndpoint: 172.30.147.5:443 status: conditions: - lastTransitionTime: "2026-03-12T21:23:37Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 12.342059ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:30:37Z" - latency: 3.991056ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:29:37Z" - latency: 12.81823ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:28:37Z" - latency: 2.89554ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:27:37Z" - latency: 1.738153ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:26:37Z" - latency: 5.674757ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:25:37Z" - latency: 14.665825ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:24:37Z" - latency: 8.168438ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:23:37Z" - latency: 2.206274ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:22:37Z" - latency: 6.587909ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.147.5:443 succeeded' reason: TCPConnect success: true time: "2026-03-12T21:21:37Z" kind: List metadata: resourceVersion: ""