https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# longhorn-storage
a
This message was deleted.
m
If PullPolicy is present then it's stuck on the version you were on when it was deployed.
q
how I can check that?
m
If it's owned by helm, you should be able to helm upgrade to 1.5.1. If it's not owned by helm, then you can use this script I wrote recently to get helm to adopt it and update it all to 1.5.1. Use at your own risk - I do not work for SUSE: https://gist.github.com/vwbusguy/494a1fca6ed72557ef7bc58a6803149c
q
😛
thanks I'll check it out
longhorn was installed with helm
m
In that case, 
helm upgrade --install longhorn longhorn/longhorn --namespace longhorn-system --create-namespace --version 1.5.1
should hopefully get you there
q
I'll do volume backups in case 🙂
m
Always a good idea to do backups 🙂
q
whatever put me in this mess....
m
you might need to also 
helm repo update
first if you don't have version 1.5.1 in your local helm yet
Hah, go easy on yourself. Messes like this are part of the fun adventure of managing stuff on kubernetes.
q
sure 😄
thanks for the good spirit
🙂 1
I am also not a big helm expert here. I see that longhorn repo is not in my list 
helm repo list
``````
m
Copy code
helm repo add longhorn <https://charts.longhorn.io>
helm repo update
It should show up after running those two
q
but why it's not there if it was installed?
m
Installed in the cluster and your local environment knowing about it until you try to install/update something are two different things, unfortunately
q
oh those repos are local not in cluster.
m
If you're running Racher UI, it'll show up in Apps>Installed Apps. Otherwise, yeah, you need to setup the helm repo locally where your kubectl is.
q
yes rancher shows it.
but too afraid of upgrading from there 🙂
m
Yeah, you should be able to upgrade to 1.5.1 in Rachner UI then from Installed Apps.
It essentially will do the same thing.
q
backup first 🙂 LOL
m
Yup!
But generally if you do kubectl from Rancher UI as well, you'll have to re-add the helm repo in that kubectl window. Same for if you download the kubeconfig and run helm locally.
b
Longhorn has three installation methods, but for upgrades, you must follow a specific approach and cannot mix them. For instance, if you installed Longhorn using 
helm chart
install longhorn, you should not perform an upgrade using the 
Rancher chart
q
Thanks for confirming!
m
They do the same thing either way. No problem with using helm CLI though. Doing it through the UI just calls helm upgrade from a pod. Here's one I ran this afternoon:
✅ 1
You can install other helm repositories in Rancher if you don't want to specifically use the Rancher shipped chart, in case you want to test a staging version of Longhorn, etc.
✅ 1
q
I used directly the chart from the longhorn GitHub
👍 1
3 Views
Open in Slack
PreviousNext
Powered by