Azure / Azure/AKS

[Feature] Managed Mesh Versioning upgrade and maintenance

Open
#5,201 26 comments 0 reactions 1 assignee Claimed by @kaarthis View on GitHub
feature-request
Dominant language
TypeScript
Stars
2.1k
Forks
395
Avg merge
2d 22h
Merged PRs (30d)
13

Description

Before Managed Mesh Upgrade and Version Management, AKS customers using Istio service mesh faced complex, multi-step upgrade procedures that required installing parallel control planes with different revisions, manually coordinating namespace relabeling from `istio-injection=enabled` to `istio.io/rev=canary`, restarting all workloads to trigger sidecar re-injection, and managing manual cleanup of old control plane components. Security patching required weeks of coordination across teams, creating extended vulnerability windows. Teams relied on spreadsheets and custom scripts to coordinate maintenance windows, with no centralized view of upgrade status across clusters. Rollback procedures required manual gateway reinstallation and complex revision tag management, risking service disruption.

Now, AKS customers can automate mesh lifecycle operations with policy-driven upgrades that handle canary orchestration seamlessly, integration with reusable maintenance configurations for predictable scheduling, and automated rollback capabilities with health-based triggers to achieve enterprise-grade operational maturity at scale while eliminating the operational overhead of manual revision management.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.