apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" generation: 126 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23343" uid: 7c01a123-035b-4a09-9bcc-a3c65383a171 spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-02-23T13:30:44Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.888776ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:30:44Z" - latency: 2.490031ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 2.09887ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 1.974996ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 1.484662ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 1.492153ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 3.536721ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:24:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23237" uid: a077515e-0c4c-42f5-81da-fbf7c22d341f spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: 172.30.95.61:443 status: conditions: - lastTransitionTime: "2026-02-23T13:30:44Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.147783ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:30:44Z" - latency: 2.630905ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 2.192533ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 3.357636ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 2.216604ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 1.332648ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 5.419094ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.95.61:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:24:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23238" uid: 446c6dcf-8738-449d-9a18-d02709dd1f08 spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-02-23T13:30:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.602596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:30:44Z" - latency: 2.837861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 5.442497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 3.574112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 3.750888ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 1.03143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 4.460777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:24:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23058" uid: 4a32110e-e1bd-4cbb-9751-13dc9959b328 spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-23T13:29:44Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 374.841µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 10.920224ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:29:44Z" - latency: 128.294µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 6.882228ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:28:44Z" - latency: 430.392µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 9.692927ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:27:44Z" - latency: 295.718µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 11.070717ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:26:44Z" - latency: 315.339µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 12.278163ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23057" uid: 4755a771-6bdf-4571-8637-754b1dad48a1 spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-02-23T13:29:44Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 307.779µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 11.219012ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:29:44Z" - latency: 469.844µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 6.324142ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:28:44Z" - latency: 263.978µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 15.957797ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:27:44Z" - latency: 226.407µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 11.016745ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:26:44Z" - latency: 286.608µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 12.1963ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-02-23T13:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23236" uid: 4bba73bb-9fbe-4ccb-acf0-3e20056fe57f spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-02-23T13:30:44Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.205494ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:30:44Z" - latency: 4.87421ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 2.485361ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 4.2162ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 2.408229ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 7.028472ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 8.198693ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:24:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23056" uid: 084aa754-ad91-4177-99a3-f760f600795e spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-02-23T13:29:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.353µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 3.84025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-23T13:29:44Z" - latency: 906.276µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 2.982826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-23T13:28:44Z" - latency: 1.444431ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 9.170173ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-23T13:27:44Z" - latency: 1.665788ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 3.408628ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-23T13:26:44Z" - latency: 7.572028ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 2.688027ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-02-23T13:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23239" uid: 21d21bcc-fc86-48e6-a8f8-af9cb4f09bd1 spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: 10.128.0.36:8443 status: conditions: - lastTransitionTime: "2026-02-23T13:30:44Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.600927ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:30:44Z" - latency: 3.433689ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 2.037968ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 3.892692ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 1.497633ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 1.03208ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 7.74296ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:24:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-02-23T13:23:43Z" 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: a649b105-b588-45b2-81ba-99a4648aee7c resourceVersion: "23240" uid: ed9f3e83-e2f8-4dcf-88f4-5deeff0b42da spec: sourcePod: network-check-source-58fb6744f5-hjhz7 targetEndpoint: 172.30.49.97:443 status: conditions: - lastTransitionTime: "2026-02-23T13:30:44Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.952647ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:30:44Z" - latency: 3.996114ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:29:44Z" - latency: 6.833056ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:28:44Z" - latency: 4.398086ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:27:44Z" - latency: 3.103839ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:26:44Z" - latency: 3.804919ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:25:44Z" - latency: 7.804702ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.49.97:443 succeeded' reason: TCPConnect success: true time: "2026-02-23T13:24:44Z" kind: List metadata: resourceVersion: ""