apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" generation: 99 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23555" uid: cf56cc27-be9a-432d-bf37-ecf5bc921e53 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-08T22:26:54Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.85955ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:26:54Z" - latency: 2.704938ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 1.266601ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 3.18109ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 1.480278ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 2.566596ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 1.144017ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:20:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23550" uid: ec3febd0-8dfe-4a87-988d-e9c9028c1925 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: 172.30.178.47:443 status: conditions: - lastTransitionTime: "2026-03-08T22:26:54Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.278771ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:26:54Z" - latency: 3.541868ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 1.748164ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 5.698592ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 1.242202ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 6.814996ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 3.311706ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.178.47:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:20:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23553" uid: feb765f9-3e70-4966-9cce-cfee691cb372 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-08T22:26:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.926082ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:26:54Z" - latency: 2.00095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 2.628866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 3.007385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 1.005055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 2.190856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 2.538759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:20:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23402" uid: ad7bcbab-7846-4645-be62-1d6b2496d059 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-08T22:25:54Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 370.699µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 10.968744ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:25:54Z" - latency: 251.486µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 9.006365ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:24:54Z" - latency: 257.466µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 9.017176ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:23:54Z" - latency: 205.315µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 10.367607ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:22:54Z" - latency: 390.24µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 26.121061ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:21:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23401" uid: 1ea3c400-ac73-4d66-aa22-bb1e9e6764d9 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-08T22:25:54Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 409.219µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 11.449195ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:25:54Z" - latency: 386.099µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 8.518013ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:24:54Z" - latency: 175.334µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 8.679267ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:23:54Z" - latency: 278.218µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 13.840715ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:22:54Z" - latency: 319.608µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 25.574076ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T22:21:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23552" uid: cad9d818-c488-4e25-affa-ac95871d32c6 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-08T22:26:54Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.704322ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:26:54Z" - latency: 3.833235ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 5.359394ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 2.066382ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 4.65989ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 4.394783ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 6.966342ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:20:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23399" uid: e03d5933-75a1-4160-813b-4d56f7709619 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-08T22:25:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.302747ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 3.506898ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T22:25:54Z" - latency: 1.494007ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 4.934263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T22:24:54Z" - latency: 3.534248ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 6.624376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T22:23:54Z" - latency: 2.235528ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 3.823138ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T22:22:54Z" - latency: 4.831514ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 6.814714ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T22:21:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23551" uid: 98a75bac-b327-4452-9a28-e501efec79ed spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: 10.128.0.38:8443 status: conditions: - lastTransitionTime: "2026-03-08T22:26:54Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.331821ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:26:54Z" - latency: 3.354303ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 2.495502ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 8.634646ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 1.394376ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 1.871199ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 5.972928ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:20:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T22:19:52Z" 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: 0ddb8058-8075-483a-b934-fc2452244c0b resourceVersion: "23554" uid: eaab9f89-8b01-4579-a28a-9b9b1cc74e27 spec: sourcePod: network-check-source-7c67b67d47-qf2dp targetEndpoint: 172.30.201.252:443 status: conditions: - lastTransitionTime: "2026-03-08T22:26:54Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.64948ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:26:54Z" - latency: 3.741213ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:25:54Z" - latency: 3.784995ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:24:54Z" - latency: 9.621891ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:23:54Z" - latency: 4.413173ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:22:54Z" - latency: 3.016247ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:21:54Z" - latency: 6.639333ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.201.252:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T22:20:54Z" kind: List metadata: resourceVersion: ""