apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" generation: 189 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "54155" uid: 6d338d5b-8eb1-40b5-9c84-b876a82bd007 spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-02-24T05:50:09Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.095807ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 2.627401ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 1.830949ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 4.653746ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 3.062383ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 3.208136ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:20:09Z" - latency: 2.342303ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:19:09Z" - latency: 8.90812ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:18:09Z" - latency: 1.82737ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:17:09Z" - latency: 2.151698ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:16:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51514" uid: a2a76de0-ef03-4aa8-8bbe-6af6ff5df175 spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: 172.30.78.149:443 status: conditions: - lastTransitionTime: "2026-02-24T05:50:09Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.541525ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 3.189286ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 2.95313ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 5.816247ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 2.923589ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 3.915695ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:20:09Z" - latency: 3.118414ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:19:09Z" - latency: 9.388193ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:18:09Z" - latency: 2.985601ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:17:09Z" - latency: 1.647875ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.78.149:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:16:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51522" uid: 2209b625-bc8d-4c73-85a2-6dfcd94a026d spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-02-24T05:50:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.129649ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 2.847347ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 2.906268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 5.514999ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 2.24177ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 1.720226ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:20:09Z" - latency: 1.699196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:19:09Z" - latency: 6.901487ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:18:09Z" - latency: 2.823256ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:17:09Z" - latency: 3.046232ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:16:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51524" uid: 3bb8011a-4dc7-4fe1-b557-d73c28dcbf1d spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-24T05:49:09Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.489268ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 15.477767ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:25:09Z" - latency: 1.228082ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 13.903425ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:24:09Z" - latency: 1.387397ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 10.395971ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:23:09Z" - latency: 1.320276ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 7.249595ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:22:09Z" - latency: 411.491µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 16.040004ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:21:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51523" uid: 9feb518d-30df-4f59-8f44-0e5d1baf41de spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-24T05:49:09Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.18801ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 14.771738ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:25:09Z" - latency: 1.390986ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 14.09017ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:24:09Z" - latency: 911.914µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 10.539024ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:23:09Z" - latency: 307.978µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 13.639819ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:22:09Z" - latency: 1.919263ms message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 13.200656ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-24T06:21:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:08Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51516" uid: b2087ba9-b7b8-4e0d-9e4c-680e3ce6b26d spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-02-24T05:50:09Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.588537ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 12.081945ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 3.878015ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 7.39438ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 3.083023ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 7.309537ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:20:09Z" - latency: 2.262211ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:19:09Z" - latency: 1.808548ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:18:09Z" - latency: 4.118191ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:17:09Z" - latency: 4.945393ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:16:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51515" uid: 8d69b382-5eca-4a8e-afa5-d2a04425c263 spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-02-24T05:49:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.609347ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 3.093373ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T06:25:09Z" - latency: 5.951101ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 2.773285ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T06:24:09Z" - latency: 2.151218ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 2.204149ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T06:23:09Z" - latency: 4.946062ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 7.302668ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T06:22:09Z" - latency: 3.103883ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 7.916584ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-24T06:21:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51520" uid: 5c56409c-0b03-429b-b7f7-046fc3ba4b3e spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: 10.128.0.35:8443 status: conditions: - lastTransitionTime: "2026-02-24T05:50:09Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.253388ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 12.28509ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 3.72554ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 7.158464ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 2.829696ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 7.702169ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:20:09Z" - latency: 4.11155ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:19:09Z" - latency: 5.623802ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:18:09Z" - latency: 5.57175ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:17:09Z" - latency: 4.668256ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:16:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-24T05:43:07Z" 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: 22108df1-f7be-4c01-83d3-1c6b04e1f28e resourceVersion: "51518" uid: 7b5a45e2-bd82-476a-bdfe-37efad488b9a spec: sourcePod: network-check-source-58fb6744f5-kn2z7 targetEndpoint: 172.30.175.58:443 status: conditions: - lastTransitionTime: "2026-02-24T05:50:09Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.084149ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:25:09Z" - latency: 3.001451ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:24:09Z" - latency: 4.293016ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:23:09Z" - latency: 7.565065ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:22:09Z" - latency: 7.514273ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:21:09Z" - latency: 7.085522ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:20:09Z" - latency: 4.166402ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:19:09Z" - latency: 2.195499ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:18:09Z" - latency: 5.424956ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:17:09Z" - latency: 5.056177ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.175.58:443 succeeded' reason: TCPConnect success: true time: "2026-02-24T06:16:09Z" kind: List metadata: resourceVersion: ""