-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot update rancher version in addon config #24
Comments
Try changing it by editing the YAML (edit the |
Tried it, the harvester UI claims that it's redeploying successfully, but the rancher version still shows as 2.8.2 instead of 2.9.4 I specified. I kept the image version as rancher/k3s:v1.27.10-k3s2 as it should be compatible with rancher v2.9.4 if I read the compatibility matrix correctly. Happens also if I manually disable and re-enable the addon. |
I did a quick test here, just bumping the rancher version to v2.9.4, and while the Harvester UI says the deployment was successful, it's actually not. One of the pods is in CrashLoopBackOff:
...and the logs say rancher v2.9.4 isn't available:
I suspect this is because rancher v2.9.4 is a Prime version release, as opposed to a Community release. The repo specified in the rancher-vcluster yaml is https://releases.rancher.com/server-charts/stable/index.yaml:
The latest v2.9.x series Rancher there is v2.9.3. To get v2.9.4, you'd need to be a Prime subscriber and update the YAML to refer to the Prime repo URL, but I can't say what that is offhand. You probably also want to update k3s to rancher/k3s:v1.27.16+k3s1 as that's the latest in the v1.27.x series, but that's unrelated -- the main issue here is whether you have access to Prime or not. |
I've deployed rancher with v2.8.2 using the vcluster addon, but I need a rancher version that supports rke2 v1.28, so at least rancher v2.8.3.
What is the recommended way to update rancher vcluster deployments? The config field in harvester isn't editable.
The text was updated successfully, but these errors were encountered: