apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" generation: 111 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "23101" uid: 1bb9308a-a995-4772-aac5-62df0c05c2df spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: 192.168.32.10:17697 status: conditions: - lastTransitionTime: "2026-03-19T09:49:16Z" message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.895715ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:49:16Z" - latency: 1.372814ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 3.156177ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 1.085317ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 904.503µs message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 3.393793ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 1.508177ms message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "23105" uid: 51221d69-3ef4-4e0e-b5f4-77d90e3d7953 spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: 172.30.137.53:443 status: conditions: - lastTransitionTime: "2026-03-19T09:49:16Z" message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.475454ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:49:16Z" - latency: 1.255591ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 8.932518ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 745.697µs message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 1.176889ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 3.21626ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 2.988762ms message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.137.53:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "23102" uid: 9dae9071-e1d6-4766-bf29-5ca02dd87d8c spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: 172.30.0.1:443 status: conditions: - lastTransitionTime: "2026-03-19T09:49:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.562447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:49:16Z" - latency: 1.837745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 11.817698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 2.170773ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 1.164409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 3.076296ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 1.460136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "22929" uid: 68158730-127a-4b28-abea-28d59fe18680 spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: api.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T09:48:16Z" message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 190.485µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 10.483856ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:48:16Z" - latency: 447.271µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 16.265157ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:47:16Z" - latency: 256.846µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 10.428575ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:46:16Z" - latency: 238.426µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 14.957225ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:45:16Z" - latency: 178.435µs message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 10.6315ms message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:44:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "22928" uid: b1712cf0-08a1-490f-b2fa-701f34fc235f spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: api-int.sno.openstack.lab:6443 status: conditions: - lastTransitionTime: "2026-03-19T09:48:16Z" message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 219.065µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 5.987617ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:48:16Z" - latency: 404.671µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 19.549537ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:47:16Z" - latency: 325.948µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 9.953932ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:46:16Z" - latency: 226.996µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 14.631517ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:45:16Z" - latency: 169.674µs message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 10.085117ms message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab successfully' reason: DNSResolve success: true time: "2026-03-19T09:44:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "23103" uid: fff12826-e61a-4677-aaf9-736cf1e3c5f7 spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: 10.128.0.4:8080 status: conditions: - lastTransitionTime: "2026-03-19T09:49:16Z" message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.75691ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:49:16Z" - latency: 2.850099ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 13.281424ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 2.788548ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 1.699161ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 5.781811ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 5.111494ms message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "22927" uid: 0b3095f8-4748-44e8-80f7-00d3dfa726e2 spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-03-19T09:48:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.052835ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 2.827959ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T09:48:16Z" - latency: 4.991893ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 9.265625ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T09:47:16Z" - latency: 5.964315ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 6.346065ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T09:46:16Z" - latency: 6.384476ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 2.199534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T09:45:16Z" - latency: 1.847426ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 5.74483ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-03-19T09:44:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "23104" uid: e5172ae9-eb37-4c45-84d3-de7d145e4b63 spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: 10.128.0.36:8443 status: conditions: - lastTransitionTime: "2026-03-19T09:49:16Z" message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.136364ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:49:16Z" - latency: 2.47858ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 14.031192ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 2.050381ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 1.701351ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 5.881483ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 5.073474ms message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:43:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-03-19T09:42:15Z" 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: 7d9506da-3989-4515-b997-bf7a1e230991 resourceVersion: "23106" uid: 6c8b2b00-cdb9-4800-9746-99d7ba8084b5 spec: sourcePod: network-check-source-b4bf74f6-wwd24 targetEndpoint: 172.30.48.131:443 status: conditions: - lastTransitionTime: "2026-03-19T09:49:16Z" message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 9.678635ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:49:16Z" - latency: 5.815652ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:48:16Z" - latency: 14.658558ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:47:16Z" - latency: 5.280239ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:46:16Z" - latency: 2.216224ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:45:16Z" - latency: 6.078938ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:44:16Z" - latency: 5.184786ms message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.48.131:443 succeeded' reason: TCPConnect success: true time: "2026-03-19T09:43:16Z" kind: List metadata: resourceVersion: ""