apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" generation: 120 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22681" uid: 5accbfb8-9998-4fc5-a876-4e6f0fec8b54 spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-20T09:02:30Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.810616ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:02:30Z" - latency: 2.58281ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 1.52656ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 1.411138ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 1.741666ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 1.917541ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:6080 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 2.765535ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:56:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22566" uid: 69417f55-e551-43f8-97b8-23a753a0926e spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: 172.30.142.0:443 status: conditions: - lastTransitionTime: "2026-03-20T09:02:30Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.771728ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:02:30Z" - latency: 2.766616ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 2.549669ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 3.139375ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 2.475517ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 2.049005ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 4.423549ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.142.0:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:56:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22569" uid: 8037847c-986f-41d8-8a00-4321293379c0 spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-20T09:02:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.854601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:02:30Z" - latency: 1.11343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 1.11242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 1.586582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 1.637094ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 912.784µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 2.098867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:56:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22426" uid: 16211188-209d-457f-a6ee-c162becdc889 spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-20T09:01:30Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 231.206µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 9.591582ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T09:01:30Z" - latency: 232.457µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 7.220484ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T09:00:30Z" - latency: 2.784685ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 7.434989ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T08:59:30Z" - latency: 179.665µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 5.174899ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T08:58:30Z" - latency: 110.463µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 52.15833ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T08:57:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22427" uid: bca7942f-5b7f-4938-b6fa-41b37a585549 spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-20T09:01:30Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 289.568µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 11.563487ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T09:01:30Z" - latency: 163.274µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 6.771312ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T09:00:30Z" - latency: 207.625µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 7.202113ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T08:59:30Z" - latency: 296.498µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 5.641011ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T08:58:30Z" - latency: 206.855µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 51.716589ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-20T08:57:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22567" uid: 7450a5e4-c67e-4e0f-8ef9-e2ef13bb62f9 spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-20T09:02:30Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.273454ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:02:30Z" - latency: 2.044676ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 1.177752ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 3.669739ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 2.438296ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 25.778222ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 8.637675ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:56:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22425" uid: 11017be4-652f-4b13-b8c8-44bbc7d4b090 spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-20T09:01:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.288485ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 4.576486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-20T09:01:30Z" - latency: 1.780118ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 2.589499ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-20T09:00:30Z" - latency: 2.123308ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 3.923286ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-20T08:59:30Z" - latency: 1.196182ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 2.977441ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-20T08:58:30Z" - latency: 6.666579ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 24.791887ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-20T08:57:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22568" uid: d6a2700c-8839-4a04-9f54-28add02bd7d9 spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: 10.128.0.36:8443 status: conditions: - lastTransitionTime: "2026-03-20T09:02:30Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.589811ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:02:30Z" - latency: 2.482748ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 2.61582ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 2.726703ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 2.910909ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 1.955041ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 2.881818ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:56:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-20T08:55:29Z" 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: 424c1c2b-bffc-4e30-984d-11b701abb7f2 resourceVersion: "22570" uid: 4ec65e10-e933-428d-a2ca-cedc23cb14fc spec: sourcePod: network-check-source-b4bf74f6-nnjv9 targetEndpoint: 172.30.15.54:443 status: conditions: - lastTransitionTime: "2026-03-20T09:02:30Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.320648ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:02:30Z" - latency: 4.36158ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:01:30Z" - latency: 2.166637ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T09:00:30Z" - latency: 2.151798ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:59:30Z" - latency: 2.225679ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:58:30Z" - latency: 4.429758ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:57:30Z" - latency: 8.09724ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.15.54:443 succeeded' reason: TCPConnect success: true time: "2026-03-20T08:56:30Z" kind: List metadata: resourceVersion: ""