This message was deleted.

what engine type is your cluster running? Typically you upgrade your charts to the latest version before doing the k8s upgrade

Yes , so basically i am using rke2 to setup cetralised cluster. And both centralised and downstream cluster are being deployed on vsphere. 1 . First i upgraded the binaries so that my rancher centralised is upgraded ( 1.30.4 ) 2. Then upgraded the rancher helm chart through stable channel 3. The above 2 steps ran perfectly and i was able to see the newer supported kubernetes version 4. Then i did the upgrade of downstream and thats when the pvc and pv started showing the above error

When I ran into this I had two issues: The vSphere creds needed to be updated for the CSI and CPI Helm charts. They required the fqdn of the account (like username@vsphere.local or whatever your domain may be) The pods for those vSphere charts I mentioned above were not running on every worker node of the cluster. I had to add some additional taints because some of my nodes had certain tolerations set and the pods would not spin up there.