06/30/2022, 5:09 PM
Hey I have a strange scenario where a cluster deployed at a site is going to be moved to another site with a different IP schema. The problem is that we do not manage the network at this site. ideally I would send someone to just rebuild the cluster but I am trying to avoid doing that. I know that this can be done by stopping kubernetes on the master node, making some config changes (deleting some stuff) and bringing it back up. Then you are able to rejoin your nodes to the master this should bring everything back. The problem is that I am currently running K3os and with it being immutable im not sure if this is even a valid option. Is there a way to just re-start the bootstrap part at the startup of K3os and I can just serve the files over the internet?


06/30/2022, 5:28 PM
1. You should not be using K3OS anymore, its a dead project. If you need an immutable OS look into opensuse MicroOS potentially. 2. I don't believe there is a way to just do the bootstrap. If your running the cluster with embedded etcd, you may just want to look into doing a snapshot and then restoring on the new cluster.


06/30/2022, 6:25 PM
Unfortunately we are behind the curve on this news and we are working on a plan to replace K3os. The lack of official notification on this really bit us in the rear as we just happened to stumble across a github issue last week that included a conversation with a Rancher representative mentioning that K3os was a dead project. Thank you for the suggestion, I will look at that as an option.
To that end Is there or will there be an upgrade path that will enable us to migrate from k3os to RancherOS v2 ( that wouldnt require us to re-image/re-build the clusters?


07/04/2022, 11:13 AM
fwiw we had a similar scenario (albeit not with k3os) and now end up just sticking our clusters behind a router, so we can control the IP space on our side