Repository navigation
Replies: 1 comment
|
See the discussion at #13485 (comment) It seems like upstream continued to add more fixes to only the 3.5 branch that they wanted users to continue to step through before upgrading to 3.6, LONG after the point where most users and projects had already made the switch. I have not seen any reports of problems upgrading from a K3s release with 3.5.26, to a release with 3.6. If you do not upgrade your cluster by replacing etcd nodes, and have always had the same members in your etcd cluster, then you do not need to worry about any of the issues in the first place. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Question: packaged K3s upgrade path versus current etcd 3.5.32 prerequisite
What is the recommended K3s upgrade path for an embedded-etcd cluster currently on
v1.33.7+k3s3(etcd3.5.26) when the current upstream 3.5 → 3.6 guide says to run all members on3.5.32or later first?I found #13485 and #13493 covering the earlier zombie-member problem and the 3.5.26 repair. This question is specifically about the newer 3.5.32 prerequisite, not a request to reopen that resolved bug.
Environment and observations
v1.33.6+k3s1tov1.33.7+k3s3, server first.3.5.26, with no endpoint errors or alarms.enable-v2override orETCD_ENABLE_V2environment setting. I cannot establish whether v2 was ever enabled historically.etcdutl3.5.32check v2store, against an unused copy including legacy snapshots and WAL, reported no custom content. Important limitation: that copy was captured while the server was running and tar noted a changing WAL file. I am not treating that as a stopped-node consistent check or proof of upgrade safety.Apparent packaging gap
The effective etcd server replacements in the inspected official K3s tags are:
v1.33.7+k3s3v3.5.26-k3s1v1.33.10+k3s1v3.5.26-k3s1v1.33.11+k3s1v3.6.7-k3s1v1.33.13+k3s2v3.6.14-k3s1Sources: the
go.etcd.io/etcd/server/v3 => github.com/k3s-io/etcd/server/v3replacements in each tag'sgo.mod, for example 1.33.10 and 1.33.11. I have not found an official K3s 1.33 intermediate embedding etcd 3.5.32.Requested guidance
etcdutl >=3.5.32 check v2storeconfirms no custom snapshot/WAL data? Or does the running-server 3.5.32 prerequisite still apply independently?v1.33.13+k3s2?The intention is to stay with official K3s releases and avoid replacing embedded etcd independently, editing datastore buckets, or using skip-check flags. Thanks for clarifying the supported path.
All reactions