Dynamic set the AKS version for management cluster - #584
Conversation
marosset
left a comment
There was a problem hiding this comment.
/lgtm
/approve
/hold for CI
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marosset, zylxjtu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test pull-e2e-capz-windows-2025-extension |
|
@zylxjtu: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
will need to check for the 2025 test failure, but it passed the manager cluster creating stage, so the fix did works, will check in anyway to unblock the main master test job failure |
|
/hold cancel |
461a0fe
into
kubernetes-sigs:master
Hard-pinning the aks version (previously --kubernetes-version 1.33.5) for CAPZ management cluster breaks CI every time AKS retires an old minor version. Set MGMT_K8S_VERSION to pin explicitly, otherwise use the region's current default GA version, falling back to the highest available version.