Hi all, in an airgapped network, I'm trying to upg...
# general
a
Hi all, in an airgapped network, I'm trying to upgrade rke2 1.28.15 to 1.29.15. When I add the plan to upgrade the control-plane, it gets hung on the first control plane. The node itself is up. When I look at rke2-server on the node it says
Waitiong for control-plane node <ip> startup: nodes <ip> not found
with the ip being the node of that control plane that I'm on. In Rancher I see errors in "Recent Events" for the rke2-canal pod running on that node. It's a lot to transcribe from an air-gapped network so I'm summarizing
Copy code
MountVolume.SetUp failed for volume "flannel-cfg" : failed to sync configmap cache: timeout waiting for condition

MountVolume.SetUp failed for volume "kube-api-access-..." : [failed to fetch token: serviceaccounts "canal" is forbidden: User "system:node:<node-hostname>" cannot create resource "serviceacccounts/token" in API group "" in the namespace "kube-system": no relationship found between node '<node-fqdn>' and this object, failed to sync configmap cache: time out waiting for the condition]
I see a few pods in CrashLoopBackOff in the cluster, which may or may not be related. helm-install-rke2-canal helm-install-rke2-coredns helm-install-rke2-ingress-nginx In both the helm-install-rke2-canal and helm-install-rke2-coredns logs they exit with this error
Copy code
Error: UPGRADE FAILED: chart requires kubeVersion: >= v1.29,15 which is compatible with Kubernetes v1.28.15+rke2r1
Oops, meant to post this in #C01PHNP149L