Update k3s to 1.33.5+k3s1 #979
Merged
Conversation
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
sd109
approved these changes
Sep 25, 2025
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.
This reverts the k3s downgrade made in #977. In azimuth-ops v0.15.0, k3s was updated to 1.33 and this azimuth-ops tag was part of the 2025.5.0 azimuth-config release. Since the latest azimuth-config tag inadvertently included k3s 1.33 (instead of 1.32), we probably can't use k3s < 1.33 for any future azimuth-ops releases (even if it would be better for compatibility with the current 1.31 CAPI cluster version in HA deployment mode) since attempting to downgrading k3s from 1.33 to 1.31 during an azimuth-config upgrade rollout may lead to unintended consequences.
The next k3s update in #928 should not be merged until the Azimuth CAPI cluster has been upgraded to at least 1.33, but ideal should be merged at the same time that the CAPI cluster is upgraded to 1.34 (CAPI cluster version is defined here).