apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" generation: 93 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21494" uid: a53a9a4a-1720-4f3a-be50-9833b62c040c spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-13T01:39:49Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.910995ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:39:49Z" - latency: 5.140053ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 4.103709ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 2.939021ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 2.732686ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 5.562787ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 894.531µs message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:33:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21246" uid: 14d53990-aff4-4e7e-a9f3-28dd058ce926 spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: 172.30.201.76:443 status: conditions: - lastTransitionTime: "2026-03-13T01:39:49Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.245428ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:39:49Z" - latency: 5.184494ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 5.172775ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 2.990142ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 1.63434ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 6.581311ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 1.543667ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.201.76:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:33:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:47Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21247" uid: 34462800-645a-492d-a3a3-c2dd4e8afc58 spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-13T01:39:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.175936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:39:49Z" - latency: 1.476816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 4.026947ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 6.598418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 3.036153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 3.610472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 3.458004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:33:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21097" uid: bbfca980-fa35-4df4-82ce-4ddf76bf6076 spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-13T01:38:49Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 316.978µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 10.520553ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:38:49Z" - latency: 1.712871ms message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 17.651265ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:37:49Z" - latency: 471.802µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 15.332959ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:36:49Z" - latency: 212.325µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 14.208772ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:35:49Z" - latency: 125.533µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 13.740305ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:34:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21098" uid: 42c59454-d527-4a88-ba5e-756f39c378ad spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-13T01:38:49Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 378.93µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 11.679401ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:38:49Z" - latency: 327.278µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 18.141156ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:37:49Z" - latency: 372.219µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 24.997822ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:36:49Z" - latency: 231.605µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 14.302755ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:35:49Z" - latency: 627.925µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 14.740507ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T01:34:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21245" uid: eeb3491a-3d39-4772-97aa-2fa0307b6342 spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-13T01:39:49Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.108981ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:39:49Z" - latency: 6.879186ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 13.803313ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 7.91827ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 5.145295ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 9.560248ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 2.540531ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:33:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21096" uid: 9bbe79ae-a97b-4a54-ae0e-dd4204604898 spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-13T01:38:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.154µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 5.085051ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T01:38:49Z" - latency: 4.563129ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 9.832047ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T01:37:49Z" - latency: 2.567882ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 7.008319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T01:36:49Z" - latency: 1.839105ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 9.674823ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T01:35:49Z" - latency: 2.094169ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 5.670649ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T01:34:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21250" uid: d6e8f953-0929-4670-8e85-f18302f5abd4 spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: 10.128.0.38:8443 status: conditions: - lastTransitionTime: "2026-03-13T01:39:49Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.672144ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:39:49Z" - latency: 6.721591ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 10.660517ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 10.955334ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 4.696893ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 14.02129ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 3.056534ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:33:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T01:32:48Z" 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: fefcd618-8713-4af7-b827-a8f244b965cb resourceVersion: "21249" uid: 572d07ea-f4a3-4488-99db-e99eed359bd1 spec: sourcePod: network-check-source-7c67b67d47-xd626 targetEndpoint: 172.30.8.233:443 status: conditions: - lastTransitionTime: "2026-03-13T01:39:49Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.462799ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:39:49Z" - latency: 7.159002ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:38:49Z" - latency: 10.300027ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:37:49Z" - latency: 11.004005ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:36:49Z" - latency: 5.246337ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:35:49Z" - latency: 14.115652ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:34:49Z" - latency: 2.09195ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.8.233:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T01:33:49Z" kind: List metadata: resourceVersion: ""