Skip to main content
Kaarthikeyan Subramanian
Senior Product Manager for the Azure Kubernetes Service
View all authors

Strengthening AKS security with platform-initiated upgrades

· 12 min read
Kaarthikeyan Subramanian
Senior Product Manager for the Azure Kubernetes Service

Azure Kubernetes Service (AKS) is introducing platform-initiated upgrades to help keep all your clusters running AKS-supported Kubernetes versions. Starting June 1, 2027, AKS upgrades clusters that remain on unsupported versions, rolling out across them in waves.

This isn't a change to what "unsupported" means. Today, a cluster that runs a Kubernetes version past its support window already stops receiving upstream patches, bug fixes, and security fixes. Platform-initiated upgrades close that gap by bringing those clusters back to a safe and supported baseline, in line with the Microsoft Secure Future Initiative and its secure-by-default principle.

The goal is to keep clusters supported, not necessarily on the newest minor version. Upgrades you plan yourself are still the best way to fit testing and timing around your workloads. This post helps you choose the approach that fits.

Enhancing Your Operating System's Security with OS Security Patches in AKS

· 6 min read
Kaarthikeyan Subramanian
Senior Product Manager for the Azure Kubernetes Service

Traditional patching and the need for Managed patching​

Operating System (OS) security patches are critical for safeguarding systems against vulnerabilities that malicious actors could exploit. These patches help ensure your system remains protected against emerging threats. Traditionally, customers have relied on nightly updates, such as unattended upgrades in Ubuntu or Automatic Guest OS Patching at the virtual machine (VM) level. However, when kernel security packages were updated, a host machine reboot was often required, typically managed using tools like kured.