apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" generation: 153 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "26146" uid: dbc170e6-3ccd-4a3d-b99c-e2460dad1968 spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-09T16:58:42Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.967963ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:58:42Z" - latency: 4.849783ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 1.519822ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 2.484919ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 4.574197ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 1.505002ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 2.364265ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:52:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "25451" uid: b9a6bbda-5922-48af-ac31-c202f7de1cff spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: 172.30.31.168:443 status: conditions: - lastTransitionTime: "2026-03-09T16:58:42Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.084454ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:58:42Z" - latency: 5.188532ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 2.131769ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 3.013773ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 7.905728ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 2.283473ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 2.737916ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.31.168:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:52:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "25449" uid: 5b80dcc2-3c2e-4290-b73d-8c4bcaa414fb spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-09T16:58:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.311244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:58:42Z" - latency: 5.320087ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 2.605563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 3.155377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 7.771745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 2.072977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 1.753789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:52:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "24900" uid: 77a8438b-908a-4ec7-a5ca-400eba2b7a4f spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-09T16:57:42Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019017ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 11.614439ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:57:42Z" - latency: 298.318µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 14.979574ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:56:42Z" - latency: 683.139µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 8.007371ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:55:42Z" - latency: 206.616µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 15.433667ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:54:42Z" - latency: 348.709µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 8.758922ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:53:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "24901" uid: cc770407-355d-42c5-a9d0-e7f7c1f71d94 spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-09T16:57:42Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 247.826µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 14.347953ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:57:42Z" - latency: 324.269µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 15.592581ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:56:42Z" - latency: 253.617µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 7.188599ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:55:42Z" - latency: 213.856µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 16.485646ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:54:42Z" - latency: 389.29µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 8.178486ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-09T16:53:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "25448" uid: 98b102a6-45b6-4083-9a91-1f0610d23b56 spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-09T16:58:42Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.00676ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:58:42Z" - latency: 8.880693ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 2.520609ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 3.011583ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 9.362419ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 2.622193ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 3.752364ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:52:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "24898" uid: 7d6f460c-8ca5-42b4-9e91-c9f3aa4ae7a0 spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-09T16:57:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.519006ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 5.003277ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-09T16:57:42Z" - latency: 4.254277ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 7.439746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-09T16:56:42Z" - latency: 820.122µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 2.233861ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-09T16:55:42Z" - latency: 2.16718ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 12.235838ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-09T16:54:42Z" - latency: 2.072686ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 3.774245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-09T16:53:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "25453" uid: 1706c7b7-e7d4-4f37-84be-6a7de6c25ac7 spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: 10.128.0.41:8443 status: conditions: - lastTransitionTime: "2026-03-09T16:58:42Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.467925ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:58:42Z" - latency: 8.73824ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 2.142309ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 2.133809ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 9.504853ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 3.853417ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 3.985001ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:52:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-09T16:51:41Z" 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: 23303cf4-db1d-46a7-94a4-88c9b4c8fc9e resourceVersion: "25452" uid: ec9757c1-3d39-4a57-afbb-ffafed8b0054 spec: sourcePod: network-check-source-7c67b67d47-d9wjb targetEndpoint: 172.30.66.14:443 status: conditions: - lastTransitionTime: "2026-03-09T16:58:42Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.023881ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:58:42Z" - latency: 8.988626ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:57:42Z" - latency: 2.606672ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:56:42Z" - latency: 4.32887ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:55:42Z" - latency: 12.120094ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:54:42Z" - latency: 4.3179ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:53:42Z" - latency: 4.236078ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.66.14:443 succeeded' reason: TCPConnect success: true time: "2026-03-09T16:52:42Z" kind: List metadata: resourceVersion: ""