apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" generation: 186 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "40106" uid: 49f522c7-7a56-4ec3-9c64-9b6812feb43f spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-18T13:41:01Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 936.255µs message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:48:01Z" - latency: 1.558322ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:47:01Z" - latency: 2.793064ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 2.153148ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 7.248712ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 4.243613ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 1.18108ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 4.969275ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:41:01Z" - latency: 1.347896ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:40:01Z" - latency: 2.554209ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:39:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "38216" uid: c5c33645-59cb-411d-9a67-67630bac732d spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: 172.30.121.139:443 status: conditions: - lastTransitionTime: "2026-03-18T13:41:01Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.48297ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:48:01Z" - latency: 1.352175ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:47:01Z" - latency: 2.464895ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 2.145267ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 2.454085ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 6.470772ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 1.812779ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 3.868985ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:41:01Z" - latency: 1.632833ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:40:01Z" - latency: 2.817036ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.121.139:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:39:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "38217" uid: 8b9cdd57-3c74-494a-afc8-186e2c98eddb spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-18T13:41:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.214012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:48:01Z" - latency: 7.979022ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:47:01Z" - latency: 11.921986ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 3.290888ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 2.828005ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 6.726429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 3.727649ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 3.858653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:41:01Z" - latency: 619.286µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:40:01Z" - latency: 3.68907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:39:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "36704" uid: 29f487dc-dc76-4c28-8d8b-cf9e53d35ce8 spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-18T13:40:01Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.52055ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 19.943709ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:46:01Z" - latency: 902.444µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 21.324246ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:45:01Z" - latency: 966.566µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 9.293417ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:44:01Z" - latency: 858.284µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 16.61945ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:43:01Z" - latency: 781.8µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 6.690488ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:42:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "36703" uid: b3ab41f8-1b80-47f2-9cc0-d19540d2822d spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-18T13:40:01Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.542961ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 24.362666ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:46:01Z" - latency: 272.757µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 25.451905ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:45:01Z" - latency: 986.277µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 12.572653ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:44:01Z" - latency: 757.69µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 17.384561ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:43:01Z" - latency: 738.029µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 9.336808ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-18T13:42:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "38213" uid: a58f4f5a-804d-4168-b4f5-8e21c2ac2dd1 spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-18T13:41:01Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.121089ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:48:01Z" - latency: 4.306485ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:47:01Z" - latency: 5.840304ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 4.214332ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 4.408607ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 6.464062ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 1.86721ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 8.487089ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:41:01Z" - latency: 3.033122ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:40:01Z" - latency: 5.068857ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:39:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "36702" uid: 0daf0da0-843d-40dd-bf99-268ca19e584b spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-18T13:40:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.10553ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 7.372345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T13:46:01Z" - latency: 1.87675ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 3.189505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T13:45:01Z" - latency: 3.226045ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 4.407708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T13:44:01Z" - latency: 1.816537ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 6.069672ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T13:43:01Z" - latency: 768.32µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 2.507256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-18T13:42:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "38218" uid: 74979992-af79-4120-b746-1f538491e67c spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: 10.128.0.40:8443 status: conditions: - lastTransitionTime: "2026-03-18T13:41:01Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059838ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:48:01Z" - latency: 2.288351ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:47:01Z" - latency: 1.50969ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 3.240166ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 3.967806ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 6.091522ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 1.374507ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 1.737827ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:41:01Z" - latency: 1.302034ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:40:01Z" - latency: 4.548353ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:39:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-18T13:33:59Z" 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: c638b1e6-897b-4df5-a4b7-de9264d6b4f8 resourceVersion: "38214" uid: aa3d70bf-fe8e-461b-a326-2831b07a26c0 spec: sourcePod: network-check-source-b4bf74f6-tw7c7 targetEndpoint: 172.30.91.49:443 status: conditions: - lastTransitionTime: "2026-03-18T13:41:01Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.958442ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:48:01Z" - latency: 2.64077ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:47:01Z" - latency: 2.554078ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:46:01Z" - latency: 2.185758ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:45:01Z" - latency: 4.361096ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:44:01Z" - latency: 7.497819ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:43:01Z" - latency: 1.645794ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:42:01Z" - latency: 1.634634ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:41:01Z" - latency: 2.824537ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:40:01Z" - latency: 5.518529ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.91.49:443 succeeded' reason: TCPConnect success: true time: "2026-03-18T13:39:01Z" kind: List metadata: resourceVersion: ""