Upgrade k3s to v1.24#2661
Draft
Copilot wants to merge 3 commits into
Draft
Conversation
Agent-Logs-Url: https://github.com/jeffborg/home-network/sessions/a739aa80-adc3-4d2a-bd37-aa489186007c Co-authored-by: jeffborg <1595430+jeffborg@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Upgrade k3s from version 1.23 to 1.24
Upgrade k3s to v1.24
May 6, 2026
Owner
|
@copilot there is a upgrade controller in here |
Agent-Logs-Url: https://github.com/jeffborg/home-network/sessions/2716fa33-9a6e-4d00-aac2-9d77dc028ec2 Co-authored-by: jeffborg <1595430+jeffborg@users.noreply.github.com>
Contributor
Author
Added upgrade
Both use the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrades the k3s release version to v1.24 across the Ansible cluster configuration and adds upgrade Plan resources for the system-upgrade-controller to automate rolling the upgrade on live nodes.
Changes
k8s/ansible/group_vars/all.yml:k3s_release_version: v1.21→v1.24(for fresh installs)cluster/core/system-upgrade-controller/plans.yaml: Addedk3s-serverandk3s-agentupgrade Plans targetingv1.24.17+k3s1cluster/core/system-upgrade-controller/kustomization.yaml: Addedplans.yamlto resources so Flux reconciles the PlansHow the upgrade works
The system-upgrade-controller Plans handle rolling the upgrade across the live cluster:
k3s-server— upgrades control-plane nodes one at a time (concurrency: 1), cordoning each node during the upgradek3s-agent— upgrades worker nodes after the server plan completes, using apreparestep to wait for servers firstBoth plans use the
rancher/k3s-upgradeimage.Notes
MixedProtocolLBServicefeature gate is retained inkube-apiserver-arg— it graduated to beta (on by default) in 1.24, but keeping it explicit is harmless and avoids any edge-case regression.xanmanning.k3srole (v2.12.1) supports k3s 1.24.