apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17:29Z" generation: 213 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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49092" uid: f20dba19-acaf-469b-8f72-91eab8596a78 spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-19T12:24:30Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.681258ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 1.626306ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 1.42241ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 1.605516ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 7.223875ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:48:30Z" - latency: 1.501713ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:47:30Z" - latency: 2.639965ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:46:30Z" - latency: 3.838779ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:45:30Z" - latency: 2.036018ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:44:30Z" - latency: 1.492262ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:43:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17: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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49093" uid: 3b25b875-06e9-4ab5-9f36-8a810915677c spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: 172.30.184.70:443 status: conditions: - lastTransitionTime: "2026-03-19T12:24:30Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.034719ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 1.490962ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 2.904413ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 5.096545ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 4.181239ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:48:30Z" - latency: 1.328458ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:47:30Z" - latency: 4.2244ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:46:30Z" - latency: 2.46801ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:45:30Z" - latency: 1.849873ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:44:30Z" - latency: 3.926492ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.184.70:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:43:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17:29Z" 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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49091" uid: e68e4935-580a-481d-a179-060f327e050f spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-19T12:24:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.894394ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 1.727919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 3.13717ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 4.356134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 1.06277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:48:30Z" - latency: 1.330117ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:47:30Z" - latency: 2.490871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:46:30Z" - latency: 792.562µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:45:30Z" - latency: 871.885µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:44:30Z" - latency: 1.985696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:43:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17: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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49598" uid: 02e8a684-410c-492a-8345-d005691bb8dd spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T12:23:30Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.943534ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:53:30Z" - latency: 6.794273ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:53:30Z" - latency: 307.088µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 14.862573ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:52:30Z" - latency: 3.576562ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 8.710757ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:51:30Z" - latency: 1.252806ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 8.359708ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:50:30Z" - latency: 803.413µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 4.733115ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:49:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17: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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49600" uid: 9b0fbae2-57fd-4086-96be-5339e5d018c2 spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T12:23:30Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 447.152µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:53:30Z" - latency: 19.937776ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:53:30Z" - latency: 2.697466ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 12.225337ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:52:30Z" - latency: 3.309964ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 8.894403ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:51:30Z" - latency: 325.24µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 9.439458ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:50:30Z" - latency: 922.716µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 4.56066ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:49:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17: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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49088" uid: 9193f1a1-d6e0-4b62-8f36-5748c72369ea spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-19T12:24:30Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.189204ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 3.548891ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 3.479648ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 1.829202ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 1.308588ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:48:30Z" - latency: 5.312451ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:47:30Z" - latency: 1.862272ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:46:30Z" - latency: 2.254674ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:45:30Z" - latency: 1.842432ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:44:30Z" - latency: 4.345153ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:43:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17: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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49599" uid: bb06133a-4222-4e21-9a76-cb214270c552 spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-19T12:23:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.662254ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:53:30Z" - latency: 3.563681ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:53:30Z" - latency: 3.633693ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 6.614439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:52:30Z" - latency: 3.935671ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 3.526ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:51:30Z" - latency: 3.001115ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 3.251572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:50:30Z" - latency: 987.338µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 4.739145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:49:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17: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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49090" uid: 0d2f66d5-8d48-4e45-91ea-d02f8d207227 spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: 10.128.0.41:8443 status: conditions: - lastTransitionTime: "2026-03-19T12:24:30Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.878763ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 1.819162ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 6.315219ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 1.462432ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 1.527903ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:48:30Z" - latency: 1.289246ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:47:30Z" - latency: 2.364317ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:46:30Z" - latency: 964.847µs message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:45:30Z" - latency: 2.189832ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:44:30Z" - latency: 4.458797ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:43:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:17: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: 373de10a-46ce-4e45-8f01-601fca4616bc resourceVersion: "49089" uid: 45ba47df-1b1b-4f69-967e-51ce0277f33b spec: sourcePod: network-check-source-b4bf74f6-5jjzp targetEndpoint: 172.30.255.78:443 status: conditions: - lastTransitionTime: "2026-03-19T12:24:30Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.144701ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:52:30Z" - latency: 5.255689ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:51:30Z" - latency: 3.465078ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:50:30Z" - latency: 2.196132ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:49:30Z" - latency: 3.84838ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:48:30Z" - latency: 1.589775ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:47:30Z" - latency: 4.251291ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:46:30Z" - latency: 2.298736ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:45:30Z" - latency: 2.532352ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:44:30Z" - latency: 3.969813ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.255.78:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:43:30Z" kind: List metadata: resourceVersion: ""