[DEV-14811] Upgrade k8s version to 1.35 #532
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Note
Medium Risk
Kubernetes version bumps can trigger control-plane/node upgrades and compatibility issues with cluster addons/workloads, and the GuardDuty addon will now change versions automatically based on upstream releases.
Overview
Upgrades the default
k8s_versionfrom1.34to1.35across AWS (variables.tfanduser_vars.auto.tfvars) and Azure (azure/variables.tf).On AWS, switches the
aws-guardduty-agentEKS addon from a hardcodedaddon_versionto dynamically using the most recent version compatible with the selected Kubernetes version viadata.aws_eks_addon_version.guardduty.Written by Cursor Bugbot for commit af07f22. This will update automatically on new commits. Configure here.