apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" generation: 267 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50533" uid: 2a460121-a8b3-427c-9b5b-add2fc8f2806 spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2025-12-05T13:03:02Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.964449ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:45:02Z" - latency: 1.202163ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 1.584832ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 2.775604ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 3.79151ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 1.722157ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 2.168658ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:39:02Z" - latency: 1.121611ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:38:02Z" - latency: 4.743358ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:37:02Z" - latency: 2.713284ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:36:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50531" uid: e3faf800-5b07-4a6c-8bf3-fc3f106bf7dc spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: 172.30.203.111:443 status: conditions: - lastTransitionTime: "2025-12-05T13:03:02Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.73242ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:45:02Z" - latency: 1.644954ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 1.462729ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 3.086743ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 4.379596ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 3.634587ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 1.502281ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:39:02Z" - latency: 5.518359ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:38:02Z" - latency: 5.804876ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:37:02Z" - latency: 2.338715ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.203.111:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:36:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50535" uid: a73a75f5-cc99-441f-8386-ee85d8de7386 spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2025-12-05T13:03:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.508244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:45:02Z" - latency: 2.202999ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 1.49697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 2.866187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 4.034228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 1.420899ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 4.534972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:39:02Z" - latency: 5.453566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:38:02Z" - latency: 4.410448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:37:02Z" - latency: 2.209101ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:36:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50087" uid: c287dbdf-8f0e-4fd8-af5e-18c846d5afc0 spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-12-05T13:02:02Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 500.904µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 8.170926ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:44:02Z" - latency: 279.357µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 4.398148ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:43:02Z" - latency: 1.167931ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 8.426584ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:42:02Z" - latency: 775.59µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 12.323458ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:41:02Z" - latency: 581.526µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 7.702547ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50086" uid: 81bcd57b-231e-49c1-8389-4c6338a443d3 spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-12-05T13:02:02Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.913µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 7.928111ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:44:02Z" - latency: 557.485µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 6.170503ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:43:02Z" - latency: 695.709µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 8.554588ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:42:02Z" - latency: 704.808µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 12.516522ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:41:02Z" - latency: 339.969µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 3.065273ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2025-12-05T13:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50532" uid: 42c20a38-10c7-4570-8a92-6e8285a934bf spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2025-12-05T13:03:02Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.566058ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:45:02Z" - latency: 1.773097ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 1.91233ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 3.536195ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 4.901419ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 1.644654ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 5.58806ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:39:02Z" - latency: 6.927646ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:38:02Z" - latency: 7.706047ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:37:02Z" - latency: 4.05713ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:36:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50085" uid: f94d242a-4831-48f4-858c-371d0c94f370 spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2025-12-05T13:02:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 917.074µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 3.249997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-05T13:44:02Z" - latency: 1.051747ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 2.608829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-05T13:43:02Z" - latency: 1.543551ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 5.070935ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-05T13:42:02Z" - latency: 1.49559ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 4.194612ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-05T13:41:02Z" - latency: 1.5191ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 3.688769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-12-05T13:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50534" uid: 16b969b5-6868-41bd-91e2-7469e476cc4a spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: 10.128.0.37:8443 status: conditions: - lastTransitionTime: "2025-12-05T13:03:02Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.409234ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:45:02Z" - latency: 2.385682ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 2.219648ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 1.89243ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 2.205759ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 2.165707ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 2.283811ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:39:02Z" - latency: 5.545929ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:38:02Z" - latency: 7.261205ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:37:02Z" - latency: 2.730095ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:36:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-12-05T12:56:00Z" 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: 491b2c8b-b620-4be0-aa31-9457efa20faa resourceVersion: "50536" uid: e711992a-1079-4504-aad1-eb82b262eb4a spec: sourcePod: network-check-source-85d8db45d4-kkllg targetEndpoint: 172.30.241.215:443 status: conditions: - lastTransitionTime: "2025-12-05T13:03:02Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.163654ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:45:02Z" - latency: 2.565738ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:44:02Z" - latency: 2.583947ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:43:02Z" - latency: 1.689535ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:42:02Z" - latency: 2.047764ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:41:02Z" - latency: 1.986253ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:40:02Z" - latency: 2.318322ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:39:02Z" - latency: 5.480208ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:38:02Z" - latency: 6.645879ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:37:02Z" - latency: 2.779586ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.241.215:443 succeeded' reason: TCPConnect success: true time: "2025-12-05T13:36:02Z" kind: List metadata: resourceVersion: ""