apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" generation: 183 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "42713" uid: aef7189b-648a-47fc-a871-4403a214c901 spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-07T21:39:29Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.949645ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 4.60352ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 2.566201ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 1.437084ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:57:29Z" - latency: 1.760333ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:56:29Z" - latency: 1.471885ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:55:29Z" - latency: 1.444905ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:54:29Z" - latency: 3.055273ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:53:29Z" - latency: 1.982607ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:52:29Z" - latency: 3.057983ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:51:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "42716" uid: cee26231-8baf-4b18-8c47-3d0df56eaaff spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: 172.30.229.121:443 status: conditions: - lastTransitionTime: "2026-03-07T21:39:29Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.151679ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 13.798821ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 3.466613ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 2.696285ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:57:29Z" - latency: 3.147246ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:56:29Z" - latency: 2.232423ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:55:29Z" - latency: 4.463768ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:54:29Z" - latency: 5.552724ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:53:29Z" - latency: 2.956012ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:52:29Z" - latency: 3.063594ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.229.121:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:51:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:28Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "42717" uid: 5a749114-6f6f-409b-8ca5-4953f13eb6e8 spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-07T21:39:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.584606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 8.903453ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 4.15702ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 1.796973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:57:29Z" - latency: 3.131275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:56:29Z" - latency: 2.170212ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:55:29Z" - latency: 1.333132ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:54:29Z" - latency: 2.161293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:53:29Z" - latency: 2.085369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:52:29Z" - latency: 2.627873ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:51:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "43758" uid: b61b0d3e-baa8-481f-816b-c39155a21d58 spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-07T21:38:29Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.853µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:02:29Z" - latency: 7.504719ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T22:02:29Z" - latency: 916.282µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:01:29Z" - latency: 9.21339ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T22:01:29Z" - latency: 1.306371ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 12.92597ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T22:00:29Z" - latency: 1.089356ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 20.941891ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T21:59:29Z" - latency: 252.696µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 11.360182ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T21:58:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "43759" uid: 9372f952-fe8f-4391-8d20-d4dc070a15de spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-07T21:38:29Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 295.377µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:02:29Z" - latency: 8.210527ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T22:02:29Z" - latency: 834.7µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:01:29Z" - latency: 8.75278ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T22:01:29Z" - latency: 1.458115ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 12.762525ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T22:00:29Z" - latency: 469.891µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 20.755178ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T21:59:29Z" - latency: 916.731µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 10.611205ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-07T21:58:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "42718" uid: 6cf60299-ec88-4fab-8b9c-915d245312f6 spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-07T21:39:29Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.083499ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 4.736954ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 1.546097ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 2.004268ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:57:29Z" - latency: 7.614582ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:56:29Z" - latency: 3.30383ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:55:29Z" - latency: 1.766623ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:54:29Z" - latency: 7.162493ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:53:29Z" - latency: 2.659705ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:52:29Z" - latency: 3.178797ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:51:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "43757" uid: 27d43429-0eea-4546-bbd2-c6616251d5de spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-07T21:38:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.082137ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:02:29Z" - latency: 3.992755ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-07T22:02:29Z" - latency: 1.051745ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:01:29Z" - latency: 4.970059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-07T22:01:29Z" - latency: 1.010064ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 4.524258ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-07T22:00:29Z" - latency: 1.562697ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 15.01363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-07T21:59:29Z" - latency: 1.687971ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 3.098884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-07T21:58:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "42714" uid: c6e36fc2-bf74-4690-abde-9999ffe39be5 spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: 10.128.0.40:8443 status: conditions: - lastTransitionTime: "2026-03-07T21:39:29Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.249508ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 9.922378ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 1.793082ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 2.813197ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:57:29Z" - latency: 6.866394ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:56:29Z" - latency: 3.177506ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:55:29Z" - latency: 4.644602ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:54:29Z" - latency: 5.281116ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:53:29Z" - latency: 1.760652ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:52:29Z" - latency: 3.176416ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:51:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-07T21:32:29Z" 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: 04ed1146-df8f-437c-b754-369c8668e094 resourceVersion: "42715" uid: 9f92ece6-f6c7-4029-8839-df483c6c53f8 spec: sourcePod: network-check-source-7c67b67d47-88mpr targetEndpoint: 172.30.158.171:443 status: conditions: - lastTransitionTime: "2026-03-07T21:39:29Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.216941ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T22:00:29Z" - latency: 9.944568ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:59:29Z" - latency: 2.003098ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:58:29Z" - latency: 4.380166ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:57:29Z" - latency: 2.998032ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:56:29Z" - latency: 10.713979ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:55:29Z" - latency: 4.513139ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:54:29Z" - latency: 6.711923ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:53:29Z" - latency: 2.449629ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:52:29Z" - latency: 3.395151ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.158.171:443 succeeded' reason: TCPConnect success: true time: "2026-03-07T21:51:29Z" kind: List metadata: resourceVersion: ""