-
Is there a recommended update policy? Should one track Talos versions, then update minor K8S versions within that? For example, I'm running now Talos 1.4.4, which ships with K8S 1.27.1. Should I update to any 1.27.x? Should I update to 1.28 when it appears? |
Beta Was this translation helpful? Give feedback.
Answered by
smira
May 18, 2023
Replies: 1 comment 3 replies
-
(Asking this because my update monitor now reports:
It's picking K8S 1.25.10, because that's the version marked as "latest" here https://github.com/kubernetes/kubernetes/releases , but I need to patch this. Should this point to the "biggest" version? Biggest within the major version?) |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a support matrix for each release of Talos: https://www.talos.dev/v1.4/introduction/support-matrix/
Also the same matrix is codified in the machinery package, if you're looking for automation.
In general, we recommend upgrading to Talos point releases, as they contain fixes. And jumping to the next minor release after some testing.
Kubernetes should stay within n-2 version support guarantee. Same way, deploy patch versions faster, minor versions with some testing.
Order of operations doesn't matter as long as you're within the supported release combination.