We have a K8S cluster running that was spun up on premise (vSphere environment) via the Rancher web GUI. All nodes are running on RancherOS and this URL was used for the OS URL in the node template: https://releases.rancher.com/os/latest/rancheros-vmware.iso. It appears when nodes are started up using Rancher on a vSphere environment that the boot device for the node is an ISO that’s created from the above ISO (though inside of the vSphere machine it calls the ISO “boot2docker.iso” when looking at the ISO it’s attached to). I had assumed that RancherOS was getting installed to disk, which explains why my attempts at upgrading the node OS via the command line wasn’t working (since it was just booting off the ISO each boot).
My question is: how would I even go about upgrading the version of RancherOS to the most current version when I’m dealing with it booting off of an ISO provisioned from the Rancher GUI? It’s not as simple as following the directions listed here as it’s booting from an ISO, not the hard drive: https://rancher.com/docs/os/v1.x/en/upgrading/
PS: I did just try to download the most current version of the VMware ISO and rename it and boot from it, but it didn’t start up properly, so something more must be going on with that ISO and it must not just be a default copy of the rancheros-vmware.iso