Replies: 1 comment
-
So I found xanmanning.k3s and rewrote it all to use ansible. To be honest this is easy enough that I went from zero to working again pretty easily. I'd probably recommend starting from that for new clusters that you care about. Makes reconfiguring it all nice and easy :) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi All,
Been experimenting with this in a 4 node RPI cluster, backed by MariaDb. Really awesome. Though definitely an experiment on the way. I'm currently struggling to figure out the best practice for 'reinstalling', or 'upgrading' the k3s installations. They seem to install helm charts, and the script has a few flags.
Particularly I am in in this state. I have 2 servers and 2 agents. I successfully have now setup the nfs subdir provisioner on a external NFS server. This is working great, so I want to make it the default storage provisioner. So I need now want to disable the local file provisioner k3s bundles. The problem is, this seems to mean running the k3s install script again, that's fine too, but now do I need to figure out the flags it was previously installed with? Is there any easy way to tell?. I know I customized it a bit to turn off klipper and use metal-lb.
Some suggestions might be 'use ansible', which I can accept would be good when starting. However following the guides that wasn't mentioned, so I am not really in that state now :)
Beta Was this translation helpful? Give feedback.
All reactions