apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:30:25Z" generation: 69 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-kubernetes-apiserver-endpoint-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "59251" uid: adf6a6c7-e405-4e27-a15d-74ad261f6577 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 192.168.34.10:17697 status: conditions: - lastTransitionTime: "2025-10-14T13:37:25Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.048184ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:25Z" - latency: 3.034988ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:25Z" - latency: 1.095655ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:25Z" - latency: 1.269569ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:25Z" - latency: 964.859µs message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:25Z" - latency: 1.087474ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:25Z" - latency: 1.194788ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:52:25Z" - latency: 1.032533ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:51:25Z" - latency: 1.015413ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:50:25Z" - latency: 1.169977ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:49:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:33:20Z" generation: 30 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-kubernetes-apiserver-endpoint-master-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "59816" uid: c84a748e-0335-4a06-8dde-9c456f7cb298 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 192.168.34.11:17697 status: conditions: - lastTransitionTime: "2025-10-14T13:40:20Z" message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.611614ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:20Z" - latency: 2.827562ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:20Z" - latency: 4.189975ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:20Z" - latency: 2.135959ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:20Z" - latency: 4.313269ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:20Z" - latency: 3.241881ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:20Z" - latency: 3.305354ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:20Z" - latency: 3.77849ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:20Z" - latency: 3.16931ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:20Z" - latency: 2.467168ms message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:52:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:48Z" generation: 135 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-kubernetes-apiserver-endpoint-master-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60363" uid: ee2a417d-348e-4d87-bf21-19b61bcdcfbe spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 192.168.34.12:17697 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.658844ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 2.288662ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 7.10389ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 3.090869ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 2.109288ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 1.880941ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 2.575371ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 4.968006ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 4.135359ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 4.807601ms message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-kubernetes-apiserver-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60362" uid: 5e0e1814-5364-4d1a-ba95-9c4e4dadc996 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 172.30.22.99:443 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.535938ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 4.465282ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 4.846517ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 4.66752ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 2.606393ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 4.164494ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 4.450919ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 5.284396ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 8.061423ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 4.288885ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.22.99:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60357" uid: 8515509e-1bfa-4106-99ff-b9982e40c8ee spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.746728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 4.502794ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 6.937325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 4.842796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 1.950453ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 2.106618ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 4.403238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 5.609996ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 11.536452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 6.085673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60736" uid: 5e0a17fb-4069-4bfc-a3e0-ea30c927215c spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: api.ocp.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-10-14T13:33:49Z" message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.676975ms message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:03:49Z" - latency: 13.821887ms message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:03:49Z" - latency: 4.382669ms message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 14.827522ms message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:02:49Z" - latency: 1.636672ms message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 8.900183ms message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:01:49Z" - latency: 1.83436ms message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 17.183046ms message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:00:49Z" - latency: 1.730046ms message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 16.496453ms message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T13:59:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60737" uid: bd6eebb1-2e8d-4706-8223-9ce45f86f9b3 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: api-int.ocp.openstack.lab:6443 status: conditions: - lastTransitionTime: "2025-10-14T13:33:49Z" message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.129398ms message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:03:49Z" - latency: 12.579947ms message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:03:49Z" - latency: 3.049647ms message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 15.762352ms message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:02:49Z" - latency: 2.037415ms message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 8.871922ms message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:01:49Z" - latency: 609.279µs message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 18.706536ms message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T14:00:49Z" - latency: 1.777757ms message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 15.512232ms message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab successfully' reason: DNSResolve success: true time: "2025-10-14T13:59:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-network-check-target-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60369" uid: 82d0948e-02d3-4f26-873f-4c571eb1acca spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 10.130.0.3:8080 status: conditions: - lastTransitionTime: "2025-10-14T13:34:50Z" message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.489618ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:50Z" - latency: 3.407519ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:50Z" - latency: 5.646202ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:50Z" - latency: 4.486635ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:50Z" - latency: 6.145928ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:50Z" - latency: 2.739308ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:50Z" - latency: 1.674582ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:50Z" - latency: 4.191272ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:50Z" - latency: 1.645591ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:50Z" - latency: 3.904124ms message: 'network-check-target-master-0: tcp connection to 10.130.0.3:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-network-check-target-master-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60364" uid: 5f9a7cfc-6f29-46cb-90a2-f53b3412dba3 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.987285ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 1.020223ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 3.246525ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 3.840484ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 1.184408ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 3.117931ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 2.822339ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 999.321µs message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 3.381507ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 1.070833ms message: 'network-check-target-master-1: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-network-check-target-master-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60367" uid: ad165556-81c6-4126-9e50-34efa88a182a spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 10.129.0.4:8080 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.471667ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 3.118049ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 1.089235ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 1.85245ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 2.558232ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 1.845919ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 1.754455ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 1.56991ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 2.192269ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 2.069215ms message: 'network-check-target-master-2: tcp connection to 10.129.0.4:8080 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60735" uid: 4efac08e-ae67-4b38-958a-823d6c4ff0f2 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2025-10-14T13:33:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.190042ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:03:49Z" - latency: 7.499968ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-10-14T14:03:49Z" - latency: 2.808709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 3.241833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-10-14T14:02:49Z" - latency: 4.599926ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 3.155711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-10-14T14:01:49Z" - latency: 2.825671ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 13.010631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-10-14T14:00:49Z" - latency: 5.999085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 6.702256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2025-10-14T13:59:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-openshift-apiserver-endpoint-master-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60359" uid: c351a36a-6fa6-4142-b603-ef265fce07a9 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 10.130.0.29:8443 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.991836ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 4.018198ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 7.291336ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 3.534264ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 3.171762ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 3.866144ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 3.592772ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 2.993204ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 5.754841ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 4.297005ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.29:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-openshift-apiserver-endpoint-master-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60358" uid: b25894d1-b1fc-45eb-8539-127ab1872264 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 10.128.0.98:8443 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.187043ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 4.117841ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 7.059939ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 4.437053ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 4.804274ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 4.230426ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 2.956863ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 4.876333ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 6.615947ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 4.792492ms message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.128.0.98:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:29:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-openshift-apiserver-endpoint-master-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60809" uid: b4be1ec3-acef-4ee6-b62d-d3a0edbfeac3 spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 10.129.0.95:8443 status: conditions: - lastTransitionTime: "2025-10-14T13:36:01Z" message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.812458ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:04:01Z" - latency: 3.032586ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:03:01Z" - latency: 1.607111ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:01Z" - latency: 1.910372ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:01Z" - latency: 1.372215ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:01Z" - latency: 1.8572ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:01Z" - latency: 3.013737ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:01Z" - latency: 2.423287ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:01Z" - latency: 2.033903ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:01Z" - latency: 1.699753ms message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.129.0.95:8443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2025-10-14T13:27:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-master-2-to-openshift-apiserver-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: master-2 uid: cdb83465-49ab-4f29-b993-ec21f35e067e resourceVersion: "60360" uid: eade6957-d7c9-4079-a326-8282bf725f8b spec: sourcePod: network-check-source-967c7bb47-bzqnw targetEndpoint: 172.30.193.169:443 status: conditions: - lastTransitionTime: "2025-10-14T13:34:49Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.440758ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:02:49Z" - latency: 4.595617ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:01:49Z" - latency: 6.591783ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T14:00:49Z" - latency: 5.818959ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:59:49Z" - latency: 2.912063ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:58:49Z" - latency: 4.98687ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:57:49Z" - latency: 3.336224ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:56:49Z" - latency: 5.016757ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:55:49Z" - latency: 8.050073ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:54:49Z" - latency: 6.034861ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.193.169:443 succeeded' reason: TCPConnect success: true time: "2025-10-14T13:53:49Z" kind: List metadata: resourceVersion: ""