apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" generation: 195 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "53307" uid: 6e8569cf-7e69-4087-aae4-cea0f0c5e384 spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-02-24T02:34:15Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.912568ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:09:15Z" - latency: 2.481239ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:08:15Z" - latency: 3.618602ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:07:15Z" - latency: 4.935639ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:06:15Z" - latency: 8.497419ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:05:15Z" - latency: 2.328106ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:04:15Z" - latency: 2.85899ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:03:15Z" - latency: 2.434228ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:02:15Z" - latency: 6.323188ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:01:15Z" - latency: 3.56628ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "51109" uid: 7b6af544-9ee5-4c29-9d5b-7161d626b33b spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: 172.30.155.242:443 status: conditions: - lastTransitionTime: "2026-02-24T02:34:15Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.93986ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:09:15Z" - latency: 4.61376ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:08:15Z" - latency: 3.649233ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:07:15Z" - latency: 3.198099ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:06:15Z" - latency: 12.318926ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:05:15Z" - latency: 3.844968ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:04:15Z" - latency: 2.231623ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:03:15Z" - latency: 4.333982ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:02:15Z" - latency: 6.306407ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:01:15Z" - latency: 6.455741ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.155.242:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "51113" uid: 7ac197e3-e05d-4a94-bf93-6791d792473b spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-02-24T02:34:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.518853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:09:15Z" - latency: 4.713412ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:08:15Z" - latency: 3.591151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:07:15Z" - latency: 3.406976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:06:15Z" - latency: 12.780599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:05:15Z" - latency: 3.761965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:04:15Z" - latency: 2.83426ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:03:15Z" - latency: 3.089686ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:02:15Z" - latency: 6.281866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:01:15Z" - latency: 4.119376ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "54173" uid: a2bd925d-883a-454b-8ad6-5573b9a3d053 spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-24T02:33:15Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.184444ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:15:15Z" - latency: 8.612751ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:15:15Z" - latency: 1.518632ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:14:15Z" - latency: 23.384155ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:14:15Z" - latency: 3.54272ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:13:15Z" - latency: 14.119745ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:13:15Z" - latency: 1.644076ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:12:15Z" - latency: 31.01332ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:12:15Z" - latency: 2.378737ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:11:15Z" - latency: 13.224191ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:11:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "54172" uid: 67492def-a32f-43e2-8191-c505df7f120d spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-24T02:33:15Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.07521ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:15:15Z" - latency: 8.799277ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:15:15Z" - latency: 1.267106ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:14:15Z" - latency: 22.394077ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:14:15Z" - latency: 355.31µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:13:15Z" - latency: 17.886371ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:13:15Z" - latency: 3.93021ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:12:15Z" - latency: 31.130574ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:12:15Z" - latency: 426.782µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:11:15Z" - latency: 16.837832ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T03:11:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:15Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "51114" uid: 029b935c-5938-4ac6-a7cb-dd60acfa9a67 spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-02-24T02:34:15Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.815179ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:09:15Z" - latency: 2.890481ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:08:15Z" - latency: 5.229947ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:07:15Z" - latency: 3.609501ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:06:15Z" - latency: 2.610063ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:05:15Z" - latency: 2.777229ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:04:15Z" - latency: 3.263141ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:03:15Z" - latency: 3.647443ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:02:15Z" - latency: 5.905886ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:01:15Z" - latency: 3.406616ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "54171" uid: de774ab8-0593-4265-a4e6-1b0ceb8b4465 spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-02-24T02:33:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.222813ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:15:15Z" - latency: 4.317981ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T03:15:15Z" - latency: 2.035107ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:14:15Z" - latency: 18.55461ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T03:14:15Z" - latency: 5.155975ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:13:15Z" - latency: 5.903705ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T03:13:15Z" - latency: 3.491418ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:12:15Z" - latency: 24.851998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T03:12:15Z" - latency: 1.805251ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:11:15Z" - latency: 8.533229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T03:11:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "51112" uid: 07355101-11e9-4e7d-9c97-3cca06b6d1b2 spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: 10.128.0.36:8443 status: conditions: - lastTransitionTime: "2026-02-24T02:34:15Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.225721ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:09:15Z" - latency: 2.576702ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:08:15Z" - latency: 4.778154ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:07:15Z" - latency: 4.071634ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:06:15Z" - latency: 15.484584ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:05:15Z" - latency: 4.892728ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:04:15Z" - latency: 2.721147ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:03:15Z" - latency: 1.981036ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:02:15Z" - latency: 5.910276ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:01:15Z" - latency: 4.040483ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:00:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T02:27:14Z" 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: 1d696bc5-f021-41a0-bb79-366f3f893636 resourceVersion: "51115" uid: 43ecb3dd-def6-4146-b03f-e4996fabfbfb spec: sourcePod: network-check-source-58fb6744f5-l4wh6 targetEndpoint: 172.30.74.186:443 status: conditions: - lastTransitionTime: "2026-02-24T02:34:15Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.918983ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:09:15Z" - latency: 2.657255ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:08:15Z" - latency: 4.800705ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:07:15Z" - latency: 6.135212ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:06:15Z" - latency: 18.110368ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:05:15Z" - latency: 4.532117ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:04:15Z" - latency: 3.748255ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:03:15Z" - latency: 3.884389ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:02:15Z" - latency: 5.857114ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:01:15Z" - latency: 3.074747ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.74.186:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T03:00:15Z" kind: List metadata: resourceVersion: ""