Skip to content

UID2-7589: update AKS guide Kubernetes version from 1.33 to 1.36 - #1050

Merged
cYKatherine merged 1 commit into
mainfrom
kchen-UID2-7589-aks-docs-k8s-version
Jul 29, 2026
Merged

UID2-7589: update AKS guide Kubernetes version from 1.33 to 1.36#1050
cYKatherine merged 1 commit into
mainfrom
kchen-UID2-7589-aks-docs-k8s-version

Conversation

@cYKatherine

Copy link
Copy Markdown
Contributor

What

Updates the AKS Private Operator integration guide (docs/guides/operator-guide-aks-enclave.md):

  • --kubernetes-version 1.331.36 in the az aks create example.
  • Expands the accompanying note so readers are not dependent on the example staying current.

Why

Azure gives each Kubernetes minor version 12 months of standard support after GA. 1.33 went GA in Jun 2025 and reached end of life in Jul 2026, so it has dropped to Long-Term Support only. A private operator following this guide verbatim now hits:

ERROR: (K8sVersionNotSupported) ... is on version 1.33.13, which is only available for
Long-Term Support (LTS). To enable LTS on the cluster, see https://aka.ms/aks/enable-lts.
Code: K8sVersionNotSupported

This surfaced as a nightly Publish All Operators failure in uid2-operator (the E2E AKS setup script carried the same stale pin — fixed in uid2-shared-actions #258). The same pin in this guide is the client-facing half of the problem, so partners standing up a new AKS private operator would fail at cluster creation.

Why 1.36

Confirmed against a live subscription with az aks get-versions --location westus3, not just the published calendar:

Version Support plans offered Notes
1.33 AKSLongTermSupport only KubernetesOfficial withdrawn — the cause of the error
1.34 KubernetesOfficial + LTS EOL Nov 2026
1.35 KubernetesOfficial + LTS EOL Mar 2027
1.36 KubernetesOfficial + LTS EOL Jun 2027, patches to 1.36.2

1.37 is not offered in the region yet. 1.36 keeps this guide aligned with the version the operator E2E now uses.

Note change

The existing note already said "be sure to use the latest supported Kubernetes version", but the stale example directly contradicted it, and a reader had no way to act on the advice. It now also:

  • explains that Azure moves each minor out of standard support on a ~12-month cadence,
  • names K8sVersionNotSupported so anyone who hits the error can search for it and land here,
  • gives az aks get-versions --location ${LOCATION} for finding what is currently available in their own region.

Scope

English only — the Japanese translation is handled by the translation pipeline and has been deliberately left untouched.

No structural, navigation, or formatting changes; the diff is confined to two lines in one file.

Ticket: UID2-7589

🤖 Generated with Claude Code

The AKS Private Operator integration guide showed --kubernetes-version 1.33
in its az aks create example. Azure gives each Kubernetes minor version 12
months of standard support after GA; 1.33 went GA in Jun 2025 and reached end
of life in Jul 2026, so it is now Long-Term Support only. A partner following
this guide verbatim would hit:

  ERROR: (K8sVersionNotSupported) ... is on version 1.33.13, which is only
  available for Long-Term Support (LTS).

Bumped the example to 1.36, the latest GA release (GA Jun 2026, EOL Jun 2027),
matching the version now used by the operator E2E setup script in
uid2-shared-actions.

Also expanded the accompanying note so readers do not depend on the example
staying current: it now explains that minor versions leave standard support on
a ~12-month cadence, names the K8sVersionNotSupported error so the failure is
searchable, and gives the az aks get-versions command for finding the versions
currently available in their region.

Japanese translation intentionally left unchanged — handled by the translation
pipeline.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@cYKatherine cYKatherine self-assigned this Jul 29, 2026
@cYKatherine
cYKatherine requested review from sunnywu and swibi-ttd July 29, 2026 03:35
@cYKatherine
cYKatherine merged commit 10d29a8 into main Jul 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants