apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" generation: 192 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "47348" uid: 2395c542-51f1-44fe-b43d-35e935e4c561 spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-08T03:36:15Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.635959ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:04:15Z" - latency: 3.652343ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:03:15Z" - latency: 1.848112ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:02:15Z" - latency: 2.229294ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:01:15Z" - latency: 3.18426ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:00:15Z" - latency: 4.622902ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 2.487671ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 2.759788ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 3.989413ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 1.351048ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "47347" uid: c429a97b-666b-4ca2-8fed-9b2b1a1ee598 spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: 172.30.61.45:443 status: conditions: - lastTransitionTime: "2026-03-08T03:36:15Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.680616ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:04:15Z" - latency: 7.662698ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:03:15Z" - latency: 4.823567ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:02:15Z" - latency: 2.556322ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:01:15Z" - latency: 1.363369ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:00:15Z" - latency: 5.179938ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 2.529332ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 1.880293ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 3.047107ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 2.580063ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.61.45:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "47349" uid: e920c31a-297f-4d61-b6d8-ae30343e9362 spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-08T03:36:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.799718ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:04:15Z" - latency: 4.432086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:03:15Z" - latency: 1.39876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:02:15Z" - latency: 1.780711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:01:15Z" - latency: 4.091756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:00:15Z" - latency: 1.596505ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 2.364857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 4.879809ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 5.593929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 3.071217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "44795" uid: bd6b3da2-178c-485b-94db-77727679fe40 spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-08T03:35:15Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 567.726µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 11.670671ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:59:15Z" - latency: 229.617µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 9.674635ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:58:15Z" - latency: 740.041µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 9.15275ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:57:15Z" - latency: 3.604303ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 8.166232ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:56:15Z" - latency: 1.049989ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - latency: 10.112257ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "44796" uid: ffcc84d9-fc4b-491b-8dbd-af4d82039141 spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-08T03:35:15Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 838.313µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 11.585489ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:59:15Z" - latency: 681.649µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 8.624845ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:58:15Z" - latency: 316.419µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 12.821014ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:57:15Z" - latency: 3.351875ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 7.913505ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:56:15Z" - latency: 804.723µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - latency: 9.741967ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:14Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "47350" uid: cdb8fa68-49c1-485e-b8b9-5778f2fa28a0 spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-08T03:36:15Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.563577ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:04:15Z" - latency: 8.09631ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:03:15Z" - latency: 5.007132ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:02:15Z" - latency: 797.823µs message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:01:15Z" - latency: 7.009809ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:00:15Z" - latency: 5.603919ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 2.46781ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 4.792536ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 4.204319ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 6.999709ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "44794" uid: 28edd084-6603-46d3-829c-847f8a615bdf spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-08T03:35:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.033016ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 4.793597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:59:15Z" - latency: 1.504003ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 2.954334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:58:15Z" - latency: 1.578535ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 4.995462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:57:15Z" - latency: 6.797883ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 4.667523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:56:15Z" - latency: 1.210395ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - latency: 7.239056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "47346" uid: f62059e9-80e2-43f9-90f6-ba9e994d1af8 spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: 10.128.0.38:8443 status: conditions: - lastTransitionTime: "2026-03-08T03:36:15Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.554747ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:04:15Z" - latency: 6.429463ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:03:15Z" - latency: 3.86855ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:02:15Z" - latency: 3.670844ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:01:15Z" - latency: 2.805499ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:00:15Z" - latency: 2.356797ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 2.517952ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 5.772224ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 6.819353ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 2.202182ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:29:13Z" 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: b4664360-7a98-4e67-95a6-3e39a3e2a113 resourceVersion: "47345" uid: 4006f88d-63bc-4223-b9de-3f8a9c04a29e spec: sourcePod: network-check-source-7c67b67d47-pts2w targetEndpoint: 172.30.127.79:443 status: conditions: - lastTransitionTime: "2026-03-08T03:36:15Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.291083ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:04:15Z" - latency: 7.695569ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:03:15Z" - latency: 1.821741ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:02:15Z" - latency: 2.003947ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:01:15Z" - latency: 2.732638ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T04:00:15Z" - latency: 4.813386ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:59:15Z" - latency: 2.336426ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:58:15Z" - latency: 5.538547ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:57:15Z" - latency: 6.243027ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:56:15Z" - latency: 2.375298ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.127.79:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:55:15Z" kind: List metadata: resourceVersion: ""