chore: bump default cluster Kubernetes versions to 1.35 (EKS) / 1.35.4 (AKS)#291
Merged
Conversation
The default `cluster_version` for AWSWorkloadClusterConfig was "1.33.0", two minors behind GA. As of 2026-05-15 the latest standard-support version on Amazon EKS is 1.35 (per https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html; 1.33 enters extended support July 2026, 1.34 in Dec 2026, 1.35 in March 2027). 1.36 is not yet GA on EKS. Also dropped the stray ".0" patch suffix to match the convention used by existing customer configs (`infra/__work__/*/ptd.yaml` set `cluster_version: 1.33` or `1.35` — minor-only). EKS accepts minor-only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`AzureWorkloadClusterConfig.kubernetes_version` defaulted to `"v1.31.1"`, which is both stale (1.31 entered extended support 2025-11-26 on AKS) and malformed (the `v` prefix is rejected by Azure ARM — existing customer configs use bare `1.32.6`/`1.35.4`, no `v`). The default was effectively dead code since every customer config in `ptd-config` explicitly sets the version, but worth fixing before someone hits it. Bumped to `"1.35.4"` to match the latest GA on AKS as of 2026-05-15. 1.36 is preview-only in eastus2 — not used as a default until it goes GA. `autoUpgradeProfile.upgradeChannel: patch` is already set on the ManagedCluster resource in `lib/steps/aks.go:233` (via `containerservice.UpgradeChannelPatch`), so AKS will auto-bump patches within the minor — no change needed there. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
timtalbot
approved these changes
May 20, 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.
Summary
Bump both cloud workload defaults to current GA:
AWSWorkloadClusterConfig.cluster_version):"1.33.0"→"1.35". Two minors behind GA; also dropped the stray.0since existing customer configs use minor-only (1.33,1.35) and EKS manages patches automatically within a minor.AzureWorkloadClusterConfig.kubernetes_version):"v1.31.1"→"1.35.4". Stale (1.31 is in extended support on AKS) and malformed — thevprefix is rejected by Azure ARM. Effectively dead code since every customer config explicitly sets a version, but worth fixing.For AKS,
autoUpgradeProfile.upgradeChannel: patchis already set inlib/steps/aks.go:233(containerservice.UpgradeChannelPatch), so AKS will auto-bump patches within the minor — no change needed.Test plan
"1.33.0"or"v1.31.1"remain (verified via grep)"1.35"is what existing EKS configs use (confirmed:grep cluster_version: infra/__work__/yields1.33and1.35)Related
🤖 Generated with Claude Code