Repository navigation
feat(blog): add platform-initiated upgrades post (draft) - #6058
Open
KAARTHIKEYAN SUBRAMANIAN (kaarthis) wants to merge 1 commit into
Open
KAARTHIKEYAN SUBRAMANIAN (kaarthis) wants to merge 1 commit into
KAARTHIKEYAN SUBRAMANIAN (kaarthis) wants to merge 1 commit into
Conversation
Draft post on AKS platform-initiated upgrades starting June 1, 2027, with guidance for multi-cluster (Fleet Manager), LTS, capacity, and workload disruption. Incorporates reviewer feedback from the Word draft. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
KAARTHIKEYAN SUBRAMANIAN (kaarthis)
requested review from
a team and
Wilson (wdarko1)
and
a balanced review from Copilot
October 30, 2026 17:31
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The guidance can omit clusters from larger fleet inventories and mislead readers about restoring unsupported clusters to support and choosing valid upgrade paths.
3 open issues
What changed in this PR
Adds a draft AKS blog post explaining platform-initiated upgrades starting June 1, 2027, and how teams can prepare unsupported clusters.
Changes:
- Explains support deadlines, upgrade eligibility, and potential workload disruption.
- Provides cluster inventory guidance and upgrade planning options using Fleet Manager, LTS, and capacity controls.
- Covers workload readiness, lifecycle notifications, and supporting documentation.
| File | Description |
|---|---|
website/blog/2026-11-12-platform-initiated-upgrades/index.md |
Adds the draft policy overview and practical upgrade preparation guidance. |
Review effort: Balanced
Comment on lines
+51
to
+61
| For a precise list, run this Azure Resource Graph query. It returns each cluster's Kubernetes version, support plan (`KubernetesOfficial` for community or `AKSLongTermSupport` for LTS), and upgrade channel: | ||
|
|
||
| ```bash | ||
| # Requires the Azure CLI resource-graph extension: az extension add --name resource-graph | ||
| az graph query -q "resources | ||
| | where type =~ 'microsoft.containerservice/managedclusters' | ||
| | project name, resourceGroup, subscriptionId, | ||
| kubernetesVersion = tostring(properties.kubernetesVersion), | ||
| supportPlan = tostring(properties.supportPlan), | ||
| upgradeChannel = tostring(properties.autoUpgradeProfile.upgradeChannel) | ||
| | order by kubernetesVersion asc" --output table |
|
|
||
| Treat upgrades like a release: development, then test, staging, and production. | ||
|
|
||
| [Azure Kubernetes Fleet Manager](https://learn.microsoft.com/azure/kubernetes-fleet/overview) is built for this. Organize your clusters into ordered stages with reusable [update strategies](https://learn.microsoft.com/azure/kubernetes-fleet/update-create-update-strategy). Stages run in order, and the groups inside a stage update in parallel. Pair a strategy with a Fleet [auto-upgrade profile](https://learn.microsoft.com/azure/kubernetes-fleet/update-automation) on the **Stable** channel, and Fleet rolls new Kubernetes versions through your environments as AKS releases them, keeping member clusters in support. |
|
|
||
| For clusters on unsupported Kubernetes versions that you still need, compare an in-place upgrade with migrating to a new, supported cluster: | ||
|
|
||
| - **In-place upgrade.** The cluster moves one minor version at a time, so a cluster that's far behind needs several upgrades. |
This branch has not been deployed
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.
Draft post on AKS platform-initiated upgrades starting June 1, 2027, with guidance for multi-cluster (Fleet Manager), LTS, capacity, and workload disruption. Incorporates reviewer feedback from the Word draft.