apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" generation: 261 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "55790" uid: 22d0fe5b-415a-4ade-9604-9c6a9f713034 spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-02-16T21:35:01Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.764685ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:10:01Z" - latency: 5.159058ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:09:01Z" - latency: 3.521764ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:08:01Z" - latency: 1.296985ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:07:01Z" - latency: 2.056166ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:06:01Z" - latency: 3.754082ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:05:01Z" - latency: 2.457236ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:04:01Z" - latency: 1.743597ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:03:01Z" - latency: 2.146849ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:02:01Z" - latency: 1.259135ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "52633" uid: 5dd26c71-fd79-4bbf-9dfd-3b3903a8633f spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: 172.30.154.147:443 status: conditions: - lastTransitionTime: "2026-02-16T21:35:01Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.547069ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:10:01Z" - latency: 5.663823ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:09:01Z" - latency: 1.813088ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:08:01Z" - latency: 1.047238ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:07:01Z" - latency: 885.014µs message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:06:01Z" - latency: 3.34662ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:05:01Z" - latency: 2.092546ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:04:01Z" - latency: 1.262764ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:03:01Z" - latency: 2.853457ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:02:01Z" - latency: 1.46783ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.154.147:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "52636" uid: cf2e1a53-91e4-4dc2-993c-6d529323c4bd spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-02-16T21:35:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.95988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:10:01Z" - latency: 6.948237ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:09:01Z" - latency: 3.818593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:08:01Z" - latency: 4.007908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:07:01Z" - latency: 1.09989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:06:01Z" - latency: 3.690339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:05:01Z" - latency: 1.821189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:04:01Z" - latency: 2.739075ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:03:01Z" - latency: 2.610651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:02:01Z" - latency: 1.183712ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "55739" uid: 35e10a89-1e23-42aa-a6b0-9d141933a968 spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-16T21:34:01Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.043µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:16:01Z" - latency: 7.610604ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:16:01Z" - latency: 1.86115ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:15:01Z" - latency: 9.989889ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:15:01Z" - latency: 370.161µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:14:01Z" - latency: 12.538828ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:14:01Z" - latency: 672.708µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:13:01Z" - latency: 5.733155ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:13:01Z" - latency: 834.663µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:12:01Z" - latency: 6.456163ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "55740" uid: 91b29b22-5659-4343-abf8-57748c1b1ee2 spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-16T21:34:01Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 686.509µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:16:01Z" - latency: 7.026179ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:16:01Z" - latency: 812.812µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:15:01Z" - latency: 10.089242ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:15:01Z" - latency: 1.957863ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:14:01Z" - latency: 10.005229ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:14:01Z" - latency: 602.386µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:13:01Z" - latency: 5.95954ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:13:01Z" - latency: 765.871µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:12:01Z" - latency: 5.994791ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-16T22:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "52631" uid: e0b852de-ca06-4532-8375-0137effc2528 spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-02-16T21:35:01Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.564059ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:10:01Z" - latency: 4.847961ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:09:01Z" - latency: 2.242351ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:08:01Z" - latency: 2.144038ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:07:01Z" - latency: 1.741607ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:06:01Z" - latency: 3.170375ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:05:01Z" - latency: 1.826889ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:04:01Z" - latency: 1.524081ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:03:01Z" - latency: 3.122834ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:02:01Z" - latency: 997.497µs message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "55738" uid: c6932f84-c2ea-47db-9bef-db8b45321114 spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-02-16T21:34:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.118649ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:16:01Z" - latency: 1.751578ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-16T22:16:01Z" - latency: 3.38338ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:15:01Z" - latency: 3.827734ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-16T22:15:01Z" - latency: 1.144431ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:14:01Z" - latency: 5.95454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-16T22:14:01Z" - latency: 1.905271ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:13:01Z" - latency: 812.033µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-16T22:13:01Z" - latency: 1.595673ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:12:01Z" - latency: 2.9682ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-16T22:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "52634" uid: d3d02cee-e2d6-4b44-90c9-481f1dc92c39 spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: 10.128.0.36:8443 status: conditions: - lastTransitionTime: "2026-02-16T21:35:01Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.802375ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:10:01Z" - latency: 7.557433ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:09:01Z" - latency: 2.046204ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:08:01Z" - latency: 1.44725ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:07:01Z" - latency: 2.364204ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:06:01Z" - latency: 3.74378ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:05:01Z" - latency: 2.131477ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:04:01Z" - latency: 6.193678ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:03:01Z" - latency: 3.389072ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:02:01Z" - latency: 2.849487ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:01:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-16T21:28:00Z" 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: c38c4104-28e6-4348-a07e-dd94820db5ac resourceVersion: "52635" uid: d2284bae-8c86-403a-8e32-dc3167774fa5 spec: sourcePod: network-check-source-7d8f4c8c66-w6tqw targetEndpoint: 172.30.246.219:443 status: conditions: - lastTransitionTime: "2026-02-16T21:35:01Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.723463ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:10:01Z" - latency: 5.872358ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:09:01Z" - latency: 3.129285ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:08:01Z" - latency: 1.851091ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:07:01Z" - latency: 941.766µs message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:06:01Z" - latency: 3.488874ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:05:01Z" - latency: 1.981854ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:04:01Z" - latency: 8.48539ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:03:01Z" - latency: 3.65099ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:02:01Z" - latency: 1.158681ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.246.219:443 succeeded' reason: TCPConnect success: true time: "2026-02-16T22:01:01Z" kind: List metadata: resourceVersion: ""