Merged
Conversation
This reverts commit c17a982.
chore: aks version update
Roopan-Microsoft
approved these changes
Mar 9, 2026
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.
Purpose
This pull request updates the AKS (Azure Kubernetes Service) deployment configuration to use a newer Kubernetes version, improves automation for node pool upgrades, and makes some minor template adjustments. The most significant change is the upgrade to Kubernetes version 1.34.2, ensuring the cluster is up-to-date with the latest features and security patches.
Kubernetes Version Upgrade:
kubernetesVersionparameter in bothinfra/main.bicepandinfra/main.jsonfrom1.32.7to1.34.2, ensuring the AKS cluster uses the latest supported version. [1] [2]Automation Improvements:
--yesflag to theaz aks nodepool upgradecommand inresourcedeployment.ps1to automate the upgrade process without manual confirmation.Template and Dependency Adjustments:
infra/main.jsonto ensure correct deployment sequencing.templateHashininfra/main.jsonto reflect the changes in the template.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information