apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" generation: 138 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24797" uid: 041a30e4-ab80-42c7-a575-633e1f3afb8b spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-08T03:46:09Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.415986ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:46:09Z" - latency: 3.749137ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 3.036158ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 2.949477ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 4.160618ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 3.247325ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 18.595594ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24518" uid: 4d6451a0-99ba-443b-8a3c-f7f2f9f8e87e spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: 172.30.100.146:443 status: conditions: - lastTransitionTime: "2026-03-08T03:46:09Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.227943ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:46:09Z" - latency: 2.930725ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 9.239918ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 5.331669ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 4.365854ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 3.243415ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 3.338857ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.100.146:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24520" uid: 8828db9f-e70f-4f7c-83d7-a3a5955cb5c2 spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-08T03:46:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.245924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:46:09Z" - latency: 3.242243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 3.422018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 2.765403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 3.477011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 2.258988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 3.320106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24369" uid: ce24b28f-8ee5-4ade-b0dd-fbbff62ff5ce spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-08T03:45:09Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 267.397µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 13.098547ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:45:09Z" - latency: 430.811µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 14.411471ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:44:09Z" - latency: 189.175µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 11.51089ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:43:09Z" - latency: 289.507µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 11.805618ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:42:09Z" - latency: 759.43µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 11.855828ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:41:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24370" uid: c23e6e9f-d523-40e4-8d6f-29d1bf3e7593 spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-08T03:45:09Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 415.19µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 15.247312ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:45:09Z" - latency: 346.389µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 14.870903ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:44:09Z" - latency: 184.385µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 12.570837ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:43:09Z" - latency: 353.199µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 11.8947ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:42:09Z" - latency: 219.006µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 11.584302ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-08T03:41:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24517" uid: 60cc0c1b-04f5-465a-89d4-7dd66dd43413 spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-08T03:46:09Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.170506ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:46:09Z" - latency: 4.573197ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 6.23857ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 5.225426ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 8.02633ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 2.820184ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 18.213544ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24368" uid: ad938a5e-2c0c-4b8b-8921-50f4c3a63310 spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-08T03:45:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.035793ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 3.265474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:45:09Z" - latency: 1.857778ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 8.815667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:44:09Z" - latency: 2.070264ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 6.535951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:43:09Z" - latency: 6.032177ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 7.638549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:42:09Z" - latency: 897.433µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 6.167651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-08T03:41:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24521" uid: 0a10739b-8eb1-4243-9ea4-23cc24f33dde spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: 10.128.0.35:8443 status: conditions: - lastTransitionTime: "2026-03-08T03:46:09Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.670348ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:46:09Z" - latency: 2.802372ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 10.87972ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 5.258037ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 7.498995ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 2.31029ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 17.939977ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.35:8443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:40:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-08T03:39:08Z" 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: e5825447-c87e-453a-9919-ced1c52a404c resourceVersion: "24522" uid: b19fd669-9704-4f38-a004-f8df5d7c228a spec: sourcePod: network-check-source-7c67b67d47-6bd2j targetEndpoint: 172.30.128.231:443 status: conditions: - lastTransitionTime: "2026-03-08T03:46:09Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.014927ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:46:09Z" - latency: 2.72765ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:45:09Z" - latency: 10.178992ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:44:09Z" - latency: 6.119289ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:43:09Z" - latency: 7.619608ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:42:09Z" - latency: 1.836338ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:41:09Z" - latency: 17.804974ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.128.231:443 succeeded' reason: TCPConnect success: true time: "2026-03-08T03:40:09Z" kind: List metadata: resourceVersion: ""