This message was deleted.
# general
a
This message was deleted.
b
That seems odd. The only supported method that I know of to upgrade imported clusters is external of Rancher. Do you have a link to the documentation that states this by chance?
And the weird events that I mentionned are, for example : (combined from similar events): MountVolume.SetUp failed for volume "kubeconfig" : requesting quota on existing directory /var/lib/kubelet/pods/ac332d81-1cd4-429b-b02c-d621329621ac/volumes/kubernetes.io~configmap/kubeconfig but different pod c566bbcf-7451-48f1-bad8-40b908b73b4a e9353c99-c70a-4cac-b621-6b21abd4d3a5 I spams it for 6 pods in the kube-system namespace on a fresh installed cluster.
OK so I don't know why the registration to Rancher does that but... It's not the case anymore with a k8s > 1.27.x I tried with 1.25 and 1.26 before.