apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" generation: 201 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "48594" uid: 24e7a32d-e016-4b7e-9329-07c20641a7b7 spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-19T09:47:05Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.870877ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 1.357087ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 3.315921ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 1.049969ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 1.229314ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:11:05Z" - latency: 6.465962ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:10:05Z" - latency: 2.655542ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:09:05Z" - latency: 2.397834ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:08:05Z" - latency: 2.140476ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:07:05Z" - latency: 8.069005ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:06:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "47989" uid: f9164d54-bdb2-4d41-9c20-5ebd46ab2567 spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: 172.30.159.191:443 status: conditions: - lastTransitionTime: "2026-03-19T09:47:05Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.067158ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 1.135462ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 4.667527ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 4.40578ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 3.714112ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:11:05Z" - latency: 5.963759ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:10:05Z" - latency: 3.971606ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:09:05Z" - latency: 2.389994ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:08:05Z" - latency: 1.324025ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:07:05Z" - latency: 8.100786ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.159.191:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:06:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "47987" uid: 19adbdcf-f483-4e1f-add6-89eb4f4420a7 spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-19T09:47:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.276437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 2.097177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 3.133704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 4.315417ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 3.891916ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:11:05Z" - latency: 1.190733ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:10:05Z" - latency: 5.265871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:09:05Z" - latency: 2.002974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:08:05Z" - latency: 3.125964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:07:05Z" - latency: 8.182379ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:06:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "48484" uid: a60e3a8f-9c34-404c-8425-1a76dbe31eae spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T09:46:05Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 621.586µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:16:05Z" - latency: 7.692419ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:16:05Z" - latency: 1.060299ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 12.563001ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:15:05Z" - latency: 762.661µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 6.745963ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:14:05Z" - latency: 895.954µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 8.801268ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:13:05Z" - latency: 835.912µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 9.399176ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:12:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "48485" uid: f91dd33a-b476-4b55-989a-0770d0e8c1d7 spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T09:46:05Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 257.727µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:16:05Z" - latency: 9.002654ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:16:05Z" - latency: 264.769µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 15.318894ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:15:05Z" - latency: 756.011µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 6.707121ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:14:05Z" - latency: 431.971µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 12.375255ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:13:05Z" - latency: 863.163µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 9.58862ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T10:12:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:05Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "47986" uid: 9495875e-c39e-49ad-a44b-b2af2e3a7774 spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-19T09:47:05Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.051041ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 1.602103ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 3.017021ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 2.379245ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 7.655887ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:11:05Z" - latency: 2.580849ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:10:05Z" - latency: 8.693983ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:09:05Z" - latency: 2.922329ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:08:05Z" - latency: 3.806323ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:07:05Z" - latency: 10.214823ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:06:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "48483" uid: 76b032a0-b81a-4279-b00d-fe31fc5f9fa6 spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-19T09:46:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.533µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:16:05Z" - latency: 5.222281ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T10:16:05Z" - latency: 1.794099ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 8.218223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T10:15:05Z" - latency: 735.54µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 2.490547ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T10:14:05Z" - latency: 1.8222ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 4.05707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T10:13:05Z" - latency: 2.487928ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 4.220535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T10:12:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "47984" uid: 3b8e80fe-be80-4e7c-b781-319ec6871d5e spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: 10.128.0.42:8443 status: conditions: - lastTransitionTime: "2026-03-19T09:47:05Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.707417ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 1.877901ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 5.010845ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 4.41718ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 4.082771ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:11:05Z" - latency: 5.949849ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:10:05Z" - latency: 1.987334ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:09:05Z" - latency: 3.218425ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:08:05Z" - latency: 3.822612ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:07:05Z" - latency: 3.631778ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:06:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:40:04Z" 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: 835b0140-093e-4eb9-96de-413b5cb01cc4 resourceVersion: "47988" uid: 94905272-9e94-40da-9513-f0642d29346c spec: sourcePod: network-check-source-b4bf74f6-tk6ns targetEndpoint: 172.30.118.91:443 status: conditions: - lastTransitionTime: "2026-03-19T09:47:05Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.576076ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:15:05Z" - latency: 1.663665ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:14:05Z" - latency: 4.47725ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:13:05Z" - latency: 3.871455ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:12:05Z" - latency: 3.843305ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:11:05Z" - latency: 2.356813ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:10:05Z" - latency: 2.113117ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:09:05Z" - latency: 4.783648ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:08:05Z" - latency: 3.633257ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:07:05Z" - latency: 9.487044ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.118.91:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T10:06:05Z" kind: List metadata: resourceVersion: ""