apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" generation: 135 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23563" uid: 6129a322-24ce-4166-aa50-b407114d9f51 spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-13T13:08:59Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.294901ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:08:59Z" - latency: 2.20055ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 2.627112ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 2.182608ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 1.152036ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 4.107358ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 2.727426ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:02:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23346" uid: 8020c944-36a3-4ec5-b390-cba811304036 spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: 172.30.51.238:443 status: conditions: - lastTransitionTime: "2026-03-13T13:08:59Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.104676ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:08:59Z" - latency: 3.622364ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 5.909445ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 3.318914ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 1.639711ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 5.017547ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 19.839752ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.51.238:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:02:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23345" uid: 210a33b4-bd30-4056-997e-fa57fcde5e94 spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-13T13:08:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.782185ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:08:59Z" - latency: 3.81989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 3.355436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 3.1936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 4.647775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 3.956843ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 19.660367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:02:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23202" uid: 5d80f516-cb4e-4cb1-9b6a-0c9077ef88a4 spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-13T13:07:59Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 324.039µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 13.425062ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:07:59Z" - latency: 797.075µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 12.808212ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:06:59Z" - latency: 654.431µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 12.266544ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:05:59Z" - latency: 148.845µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 11.15627ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:04:59Z" - latency: 340.261µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 17.540339ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:03:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23200" uid: 9615ac4d-cf3b-433c-90b0-61a3f126d0bd spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-13T13:07:59Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 431.283µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 13.715541ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:07:59Z" - latency: 416.853µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 12.976828ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:06:59Z" - latency: 341.421µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 11.105718ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:05:59Z" - latency: 218.317µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 10.355774ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:04:59Z" - latency: 392.173µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 18.422057ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-13T13:03:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23344" uid: f7008b9e-1041-41c2-9ea9-e75bdb584884 spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: 10.128.0.3:8080 status: conditions: - lastTransitionTime: "2026-03-13T13:08:59Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.551209ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:08:59Z" - latency: 6.36647ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 8.453915ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 4.141389ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 2.848549ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 6.326059ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 20.775931ms message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:02:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23201" uid: 505752e9-81f0-4a81-9d4c-77ed326ae101 spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-13T13:07:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.231493ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 6.739332ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T13:07:59Z" - latency: 5.891135ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 4.496781ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T13:06:59Z" - latency: 6.103932ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 5.255605ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T13:05:59Z" - latency: 1.229558ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 5.812902ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T13:04:59Z" - latency: 5.769971ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 7.592349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-13T13:03:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23348" uid: 54449cb1-9e54-4456-90b3-6b0a847d5507 spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: 10.128.0.42:8443 status: conditions: - lastTransitionTime: "2026-03-13T13:08:59Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.461849ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:08:59Z" - latency: 4.404179ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 12.412489ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 5.76103ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 5.190432ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 6.931607ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 20.838493ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:02:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-13T13:01:58Z" 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: 0fa0cd06-0713-4d9c-bbbe-93031eeb0b8d resourceVersion: "23349" uid: af7720ac-dcb9-46f2-8c72-0b8ec86bf3fd spec: sourcePod: network-check-source-7c67b67d47-7gg49 targetEndpoint: 172.30.231.153:443 status: conditions: - lastTransitionTime: "2026-03-13T13:08:59Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.148968ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:08:59Z" - latency: 3.79699ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:07:59Z" - latency: 12.531344ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:06:59Z" - latency: 6.331428ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:05:59Z" - latency: 6.046509ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:04:59Z" - latency: 5.904956ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:03:59Z" - latency: 20.73206ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.231.153:443 succeeded' reason: TCPConnect success: true time: "2026-03-13T13:02:59Z" kind: List metadata: resourceVersion: ""