Closed MarkusGeigerDev closed 2 years ago
The k3os-latest
Plan is an outstanding intent to mutate your cluster subject to, by default, resolution of the "latest" tag k3OS tag on github. If you would rather avoid the side-effects of unintended mutations I encourage you to:
k3os-latest
node-selector (it will get redeployed on upgrade unless you take steps to delete it from your server nodes before k3s starts. if the redeployed manifest has a timestamp newer than your latest edit it will most likely get overwritten)Additionally, the SUC does not attempt to determine if a version is newer than what is currently installed, only that it is different. Another good reason to orchestrate upgrades with a plan that you control :smiley: (rancher-orchestrated upgrades for k3s and rke2 do exactly this but, sadly, k3OS upgrades are not supported)
Version (k3OS / kernel) k3os version v0.21.1-k3s1r0
Architecture Raspberry Pi 3B+
Describe the bug If a node has the
k3os.io/upgrade=enabled
label set, the auto-upgrade controller always applieshttps://github.com/rancher/k3os/releases/latest
, even if the current release is newer (i.e. a pre-release), therefore effectively downgrading the system. This should not happen.To Reproduce
latest
(i.e. pre-release, like v0.21.1-k3s1r0 at the time of writing)latest
Expected behavior The auto-update controller should ignore
latest
versions that are earlier than the current versionActual behavior The auto-update controller always applies
latest
, even if that results in a downgrade