apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" generation: 108 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22571" uid: 1534a0bc-cddf-4537-aeb8-0f7ec48a0013 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-19T12:21:19Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.894782ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:21:19Z" - latency: 2.111603ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 3.440523ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 1.482876ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 4.480239ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 2.944341ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 1.092827ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:15:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22569" uid: 693bce48-05b8-49ab-b3df-7246b5d4eaf5 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: 172.30.72.2:443 status: conditions: - lastTransitionTime: "2026-03-19T12:21:19Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 9.580717ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:21:19Z" - latency: 1.795295ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 5.153636ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 2.638584ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 5.635817ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 4.746296ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 1.217969ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.72.2:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:15:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22568" uid: df695e06-1bb1-4dc0-bc8c-ce939b4fc815 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-19T12:21:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.337943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:21:19Z" - latency: 5.767634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 3.397583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 1.554398ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 6.19481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 4.54497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 4.8922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:15:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22402" uid: 12476adb-5bc9-4be4-bc09-f3e3505df525 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T12:20:19Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 212.955µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 11.809543ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:20:19Z" - latency: 148.744µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 10.477496ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:19:19Z" - latency: 200.814µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 8.758874ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:18:19Z" - latency: 234.375µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 16.555692ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:17:19Z" - latency: 447.262µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 8.142248ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:16:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22403" uid: 71cf7e5f-d5f0-4cf9-ab07-997a13d7d720 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T12:20:19Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 204.266µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 14.274033ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:20:19Z" - latency: 205.015µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 7.269748ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:19:19Z" - latency: 150.074µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 9.278887ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:18:19Z" - latency: 138.513µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 16.210082ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:17:19Z" - latency: 214.775µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 7.861381ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T12:16:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22570" uid: 0e9cb829-7b2d-4372-beb2-49b79b13b8c3 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-19T12:21:19Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.541885ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:21:19Z" - latency: 6.527882ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 4.982672ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 2.273066ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 5.709299ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 4.012948ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 5.144565ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:15:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22401" uid: 4ad80746-2fec-4b77-9aba-c224542e1927 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-19T12:20:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.435845ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 9.204728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:20:19Z" - latency: 1.19811ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 3.138566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:19:19Z" - latency: 880.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 2.741697ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:18:19Z" - latency: 1.648ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 7.323358ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:17:19Z" - latency: 4.416527ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 3.919155ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T12:16:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22573" uid: 321b96dc-0307-46d8-981c-389999117167 spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: 10.128.0.39:8443 status: conditions: - lastTransitionTime: "2026-03-19T12:21:19Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.958996ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:21:19Z" - latency: 1.61747ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 5.083474ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 2.674565ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 5.174936ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 2.764497ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 4.89639ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:15:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T12:14:18Z" 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: 41b47749-a7d7-429f-9c0a-3925a76dc079 resourceVersion: "22572" uid: 908f7c6e-686d-4d2f-bd19-df66dcd22f3a spec: sourcePod: network-check-source-b4bf74f6-llsdf targetEndpoint: 172.30.112.15:443 status: conditions: - lastTransitionTime: "2026-03-19T12:21:19Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.110824ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:21:19Z" - latency: 6.503481ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:20:19Z" - latency: 6.024157ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:19:19Z" - latency: 1.825194ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:18:19Z" - latency: 5.637307ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:17:19Z" - latency: 3.085115ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:16:19Z" - latency: 6.660801ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.112.15:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T12:15:19Z" kind: List metadata: resourceVersion: ""