Azure Container Services Docs – Weekly Update (2026-06-07 to 2026-06-14)
The most meaningful Azure Kubernetes Service, AKS Arc, Container Registry, Application Gateway for Containers, and Fleet Manager documentation changes from the last 7 days. AKS everywhere! Summaries are AI-filtered to skip trivial edits.
📊 Updates this week: ACR (12), AGC (1), AKS (71), Fleet (1)
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation has been updated to clarify the use of the application routing add-on for AKS, improving the guidance provided to users. |
||
|
|
||
|
Security ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary The document clarifies that certain add-ons requiring access to the IMDS endpoint are not supported with IMDS restriction, providing critical information for users configuring their AKS clusters. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-12 06:07 |
||
|
Summary The documentation for Azure Kubernetes Service (AKS) for Extended Zones has been updated to reflect that AKS is now generally available for both public and private clusters. Users can now deploy a private AKS cluster in an Azure Extended Zone by using the `–enable-private-cluster` flag in the Azure CLI command. Additionally, the API version has been updated to "2024-09-01," ensuring users have access to the latest features and improvements. |
||
|
|
||
|
Networking ✨ Update Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now explicitly states that injecting non-Microsoft-managed sidecars, such as custom telemetry, logging, or security agents, into the Istio gateway proxy pods managed by the application routing add-on is not officially supported. Users should be aware that if they choose to proceed with this injection, Microsoft will only provide best-effort support for any resulting issues. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The document has been revised to include detailed explanations of LocalDNS, an advanced feature in AKS that improves DNS resolution. This update enhances the understanding of DNS management in AKS environments. |
||
|
|
||
|
Networking 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now includes important notes regarding the configuration of Prometheus/Grafana instances, highlighting that certain dashboard panels may need specific adjustments to display all data correctly. Additionally, it clarifies that Cilium does not support DNS metrics or dashboards, which is crucial for users relying on these features for network observability. |
||
|
|
||
|
Storage ✨ Update Modified: 2026-06-12 06:03 |
||
|
Summary This document outlines storage options and configurations for Azure Container Registry, helping users optimize their container storage solutions. |
||
|
|
||
|
Compliance 🆕 New Modified: 2026-06-12 22:11 |
||
|
Summary This new document outlines the retirement of the preview property `enableCustomCATrust` in AKS, providing important information for users relying on this feature. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary This document has been revised to clarify the ingress networking in AKS, including the recommended production-ready defaults for most workloads and the differences between AKS Automatic and AKS Standard modes. |
||
|
|
||
|
Security 🆕 New Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now includes standardized terminology for add-ons, specifically regarding the AzurePodIdentityException, which allows certain pods to access the Azure Instance Metadata Service without interception. This enhances the understanding of pod-managed identity in AKS. |
||
|
|
||
|
Storage 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now includes details about the `managed-csi-premium-v2` storage class, which utilizes Azure Premium SSD v2 with locally redundant storage (LRS) for creating managed disks. Users can now understand that this storage class ensures the underlying Azure Disk is deleted when the associated persistent volume is deleted, and it is available starting with Kubernetes version 1.35. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The document has been updated to reflect new considerations for MLOps in AKS, including guidance for both AKS Automatic and AKS Standard, enhancing the clarity of how to apply MLOps practices in Azure Kubernetes Service. |
||
|
|
||
|
Security 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The security concepts document has been updated to include new security components and practices in AKS, enhancing the understanding of identity, authorization, and workload protection. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-12 22:11 |
||
|
Summary The documentation has been updated to reflect new retirement dates for Windows Server 2022 in Azure Kubernetes Service (AKS). Users should note that support for Windows Server 2022 node pools will end on June 30, 2028, and it will not be supported in Kubernetes version 1.37 and later. Additionally, all existing node images for Windows Server 2022 will be removed on June 30, 2029, which will impact scaling operations. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation has been updated to standardize the terminology from ‘addon’ to ‘add-on’ for virtual nodes, improving consistency across the documentation. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now includes a detailed comparison of the two AKS cluster modes—AKS Automatic and AKS Standard—highlighting their differences in operations, node management, upgrades, security, monitoring, and networking. Users can now better understand which mode to choose based on their needs for production readiness, customization, and operational control when deploying AI and ML workloads on Azure Kubernetes Service. Additionally, the section on designing and deploying AI and ML workloads has been expanded to emphasize the benefits of using AKS for high-performance infrastructure and improved operational reliability. |
||
|
|
||
|
Security 🆕 New Modified: 2026-06-12 22:11 |
||
|
Summary The documentation now includes updated information regarding the retirement of the `enableCustomCATrust` (preview) feature. Users are instructed to update their node pools and clusters by using the `–disable-custom-ca-trust` parameter in the `az aks nodepool update` and `az aks update` commands. Additionally, if users wish to enable Custom CA Trust after the retirement, they can do so by using the `–custom-ca-trust-certificates` parameter and providing a path to a certificate file. |
||
|
|
||
|
General ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary The description for the virtual nodes add-on has been standardized, changing ‘addon’ to ‘add-on’, which enhances the clarity and consistency of the documentation. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now includes support for AKS on bare metal in preview, expanding the list of supported distributions for Kubernetes Fleet integration. Users can now explore this new option alongside existing services like EKS, GKE, K3s, OCP, and Rancher. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The overview of security bulletins has been updated to standardize terminology regarding AKS add-ons, enhancing clarity and consistency in documentation. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary This document has been updated to include best practices for MLOps in AKS, providing guidance for both AKS Automatic and AKS Standard modes. |
||
|
|
||
|
Storage 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now clarifies that the built-in storage classes for AKS include the new `managed-csi-premium-v2` storage class, effective with Kubernetes version 1.35, which provisions Premium SSD v2 disks designed for I/O-intensive workloads. Additionally, it specifies that starting with Kubernetes version 1.29, AKS uses zone-redundant storage (ZRS) for managed disks across availability zones, enhancing data resilience, though at a higher cost compared to locally redundant storage (LRS). Users are now informed that they can create a new storage class with the LRS SKU for cost optimization if needed. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-12 06:03 |
||
|
Summary This document has been updated with new author metadata, ensuring proper attribution. The content remains technically relevant and accurate. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary This update standardizes add-on terminology in the documentation, specifically changing ‘add on’ to ‘add-on’ for consistency. It also includes an example YAML configuration for Azure Managed Prometheus as a DaemonSet. |
||
|
|
||
|
Networking ✨ Update Modified: 2026-06-12 22:20 |
||
|
Summary The documentation now clarifies that for associations created on or after April 23, 2026, Network Security Groups (NSGs) are fully supported on the Application Gateway for Containers association subnet, including both inbound and outbound rules. Additionally, it specifies that "Deny all" rules can block traffic on ports 80 and 443 unless explicit allow rules are defined, which may prevent access to the frontend and impact communication with the AKS cluster. Users are advised to ensure that the _AzureLoadBalancer_ service tag is allowed to maintain proper gateway operations. |
||
|
|
||
|
Security ✨ Update Modified: 2026-06-12 06:03 |
||
|
Summary This document discusses the use of managed identities for authenticating with Azure Container Registry, providing a secure method for accessing container images. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now clarifies that while Microsoft Support can offer general guidance on the application and evaluation of custom Azure Policy definitions within AKS, they will not provide detailed troubleshooting for customer-authored policy logic, including Rego-based policies. This change informs users that they may need to independently analyze or explain the behavior of their specific policies regarding workload permissions. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for Deployment Safeguards in Azure Kubernetes Service (AKS) has been updated to clarify the behavior of Deployment Safeguards in different AKS modes. Users can now see that in AKS Automatic mode, Deployment Safeguards are enabled by default in `Enforce` mode, while in AKS Standard mode, they are optional and can be set to either `Warn` or `Enforce`. Additionally, the documentation now specifies that users can exclude certain namespaces from Deployment Safeguards and Pod Security Standards, but cannot change the safeguard level from `Enforce` to `Warn` in AKS Automatic clusters. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now includes detailed descriptions of the two cluster modes available in Azure Kubernetes Service (AKS): AKS Automatic and AKS Standard. Users can choose AKS Automatic for a fully managed experience with reduced operational overhead and preconfigured defaults, or AKS Standard for greater flexibility and control over cluster configuration and operations. Additionally, the documentation highlights the differences in service-level agreements (SLAs) between the two modes, providing users with clearer guidance on which mode to select based on their operational needs. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary The documentation has been updated to provide clearer guidance on migrating from the Open Service Mesh (OSM) add-on to the Istio add-on for Azure Kubernetes Service (AKS). Users can now find detailed instructions on how to translate OSM configurations to Istio equivalents, including specific commands for enabling and disabling add-ons, labeling namespaces, and applying translated Istio resources. Additionally, the article emphasizes the importance of planning for service disruption during the migration process and includes a structured approach for verifying the state of the OSM and Istio add-ons throughout the transition. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-06-12 06:03 |
||
|
Summary The documentation for the Azure Container Registry RBAC built-in roles has been updated to clarify the permissions associated with using the `az` CLI, specifically regarding the `az acr login` command. Users are now informed that while this command can succeed with the specified role in an ABAC-enabled registry, it does not grant data plane operations (pull, push, delete) unless the identity also holds an ABAC-compatible data plane role. Additionally, the customer intent description has been refined for clarity, emphasizing the management of role assignments and permissions for container resources. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-12 06:03 |
||
|
Summary The document has been updated to improve clarity and consistency in the author metadata, which enhances the overall quality of the documentation. |
||
|
|
||
|
Networking ✨ Update Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now explicitly states that injecting non-Microsoft-managed sidecars, such as custom telemetry, logging, or security agents, into the Istio ingress gateway proxy pods managed by the add-on is not officially supported. Users should be aware that if they choose to inject their own sidecar into a managed proxy pod, Microsoft will only provide best-effort support for any issues that arise. |
||
|
|
||
|
Operations ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for the Azure Monitor metrics add-on has been updated to clarify that the `Minimal ingestion profile` setting is enabled by default for add-on-based collection, specifically focusing on control plane metrics. Additionally, the terminology has been standardized to consistently refer to the "add-on" instead of "addon," which may enhance user understanding of the feature. Users can now expect clearer guidance on the default targets and metrics collected when this profile is enabled. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-12 06:03 |
||
|
Summary This tutorial has been updated to improve clarity regarding the use of customer-managed keys in Azure Container Registry, providing users with better guidance. |
||
|
|
||
|
General 🗑️ Removal Modified: 2026-06-12 06:03 |
||
|
Summary This document has been updated to clarify the deprecation of content trust in Azure Container Registry, providing users with essential information regarding changes in functionality. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The description for Istio service mesh latency comparisons has been updated to standardize terminology, changing ‘addon’ to ‘add-on’. This improves clarity and consistency in the documentation. |
||
|
|
||
|
General ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary This update standardizes the terminology for the Azure Keyvault Secrets Provider add-on, improving consistency across documentation and enhancing user understanding of integration options. |
||
|
|
||
|
Security ✨ Update Modified: 2026-06-12 06:07 |
||
|
Summary The documentation now clarifies that when using `WorkloadIdentityCredential`, users must pass scopes in the Microsoft Entra ID v2 format `<resource>/.default`, such as `https://management.azure.com/.default`, to avoid failures associated with raw resource URIs. Additionally, it details how to use identity bindings and direct federation within the same workload by projecting a second service account token with the audience `api://AzureADTokenExchange`, allowing for more flexible identity management configurations. |
||
|
|
||
|
Operations 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now includes a new tip on using automatic Pod Disruption Budget (PDB) management to prevent quarantine scenarios during pod eviction. By automatically scaling up deployment replicas to meet PDB constraints before the drain begins, users can ensure that eviction proceeds without blocking, thus eliminating the need for manual quarantine resolution. This enhancement provides users with a more efficient way to manage pod disruptions. |
||
|
|
||
|
General ✨ Update Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now clarifies that injecting non-Microsoft-managed sidecars, such as custom telemetry, logging, or security agents, into the ingress-nginx proxy pods managed by the add-on is not officially supported. Users should be aware that if they choose to proceed with this injection, Microsoft will only provide best-effort support for any resulting issues. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-12 06:03 |
||
|
Summary This document has been updated with new author metadata, ensuring proper attribution. The content remains technically relevant and accurate. |
||
|
|
||
|
Operations ✨ Update Modified: 2026-06-12 06:03 |
||
|
Summary This document provides troubleshooting steps for issues related to connected registries in Azure Container Registry, enhancing user experience and operational efficiency. |
||
|
|
||
|
Operations ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for upgrading the OS version in Azure Kubernetes Service (AKS) has been updated to remove the `–node-count` parameter from several command examples. Users can now focus on specifying the node pool name without needing to include the node count, simplifying the command syntax for node pool updates. Additionally, the Kubernetes version references have been streamlined, enhancing clarity in the upgrade process. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-12 06:03 |
||
|
Summary The document has been updated to improve clarity and consistency in the author metadata, which enhances the overall quality of the documentation. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for securing outbound traffic from Azure Kubernetes Service (AKS) has been updated to standardize terminology, specifically changing "addons" to "add-ons" throughout the article. Additionally, the requirements for the CSI Secret Store add-on pods to communicate with Azure Key Vault have been clarified, ensuring users understand the necessary endpoints and their significance for both standard and government cloud environments. |
||
|
|
||
|
Compute ✨ Update Modified: 2026-06-11 19:00 |
||
|
Summary Learn how to profile GPU workloads with real-time observability and analyze flame graphs to identify memory hotspots to optimize GPU workloads. |
||
|
|
||
|
Operations 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary This new document introduces Automatic Pod Disruption Budget management in AKS, detailing how it automates PDB management during upgrades to protect application availability. It explains the functionality of creating PDBs automatically and scaling replicas to satisfy disruption budgets. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for the Azure Kubernetes Service (AKS) has been updated to standardize terminology related to add-ons, ensuring consistency throughout the content. Additionally, the operational impacts of certain security configurations, such as password expiration and inactive password locking for the root user, have been clarified to emphasize their potential to disrupt AKS add-on functionality and prevent nodes from joining the cluster. Users should review these changes to understand the implications of these configurations on their AKS deployments. |
||
|
|
||
|
Cost 🆕 New Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now includes a detailed comparison of AKS cluster modes, specifically highlighting the differences in reliability features between AKS Automatic and AKS Standard. Users can better understand how to configure their clusters, as AKS Automatic offers preconfigured reliability defaults while AKS Standard requires explicit management of features like node autoprovisioning and workload scaling. Additionally, the article emphasizes the importance of application-specific settings, such as Pod Disruption Budgets and resource requests, to ensure high availability and resilience in both cluster modes. |
||
|
|
||
|
Cost ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary The documentation for best practices in cluster security for Azure Kubernetes Service (AKS) has been updated to clarify the differences in security responsibilities between AKS Automatic and AKS Standard modes. Users can now find detailed guidance on securing API server access, managing upgrades, and maintaining node security, emphasizing the preconfigured defaults in AKS Automatic versus the explicit configurations required in AKS Standard. Additionally, the section on upgrade processes has been enhanced to highlight the importance of monitoring impacts when upgrading Kubernetes versions. |
||
|
|
||
|
General ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary This update includes improvements to the documentation regarding the Node Problem Detector, enhancing user understanding of its functionality and usage in AKS. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now clarifies that both Deployment Safeguards and Pod Security Standards can be enforced in either enforcement or warning mode, enhancing flexibility for users managing Kubernetes best practices in their AKS clusters. Additionally, it introduces the Istio-based service mesh add-on for AKS as an optional ingress gateway, providing users with more options for managing ingress traffic. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for the Istio-based service mesh add-on in Azure Kubernetes Service has been updated to standardize terminology, specifically changing "addon" to "add-on." Additionally, it clarifies that for existing clusters using a self-signed root certificate generated by Istio CA, switching to a plugin CA is not supported without first disabling and then re-enabling the mesh. Users can now better understand the requirements for using their own certificates and keys with the Istio CA. |
||
|
|
||
|
Operations ✨ Update Modified: 2026-06-11 19:00 |
||
|
Summary This document outlines monitoring strategies for Azure Kubernetes Service (AKS), including author updates and best practices for effective monitoring. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The document has been updated to standardize terminology regarding add-ons in AKS, improving clarity and consistency across the documentation. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary The best practices document has been updated to include guidance for both AKS Automatic and AKS Standard modes, emphasizing the differences in implementation responsibilities and providing a structured comparison of features and controls for each mode. |
||
|
|
||
|
Security ✨ Update Modified: 2026-06-12 06:07 |
||
|
Summary The documentation now clarifies that when updating application code from managed identity token acquisition to `WorkloadIdentityCredential`, users must utilize Microsoft Entra ID v2 scopes in the format `<resource>/.default`, rather than just the resource URI. Additionally, it specifies the audience for projected service account tokens, indicating that identity bindings and direct workload identity federation use different audiences, which may require separate service accounts or additional token volumes for workloads needing both authentication paths. |
||
|
|
||
|
Networking 🆕 New Modified: 2026-06-11 22:19 |
||
|
Summary The document now includes standardized terminology for the Istio-based service mesh add-on, enhancing clarity regarding compatibility with AKS clusters. |
||
|
|
||
|
Networking ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary This update standardizes terminology for add-ons in the context of L7 Policies using AKS and Istio. It also enhances the content related to Container Network Observability features, providing clearer guidance for users. |
||
|
|
||
|
Operations 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now includes a new section on "Automatic PDB management (preview)," which allows users to automate the management of Pod Disruption Budgets (PDBs) during AKS upgrade drains. This feature enables automatic scaling of deployment replicas to satisfy disruption budgets when a PDB blocks eviction on a cordoned node, and it can also create PDBs for deployments that lack them, enhancing workload protection during upgrades. Users can find installation and configuration details linked within the section. |
||
|
|
||
|
Networking ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary This update standardizes the terminology used for add-ons in the Azure Kubernetes Service documentation, improving consistency and clarity for users configuring Azure CNI. |
||
|
|
||
|
Compute ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary The documentation now correctly specifies the `–drain-timeout` parameter for setting the node drain timeout in minutes when using the `az aks nodepool add` and `az aks nodepool update` commands. Previously, the parameter was incorrectly referred to as `–drain-time-out`, which could lead to confusion for users attempting to configure node pools. This change ensures that users can accurately set the timeout values of 100 or 45 minutes without encountering errors. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for cost optimized add-on scaling in AKS has been updated to clarify the installation of the Vertical Pod Autoscaler (VPA) add-on, which allows supported add-ons to autoscale based on usage. Users are now advised to ensure sufficient compute resources in the system node pool and to consider enabling the cluster autoscaler or node autoprovisioning for optimal resource management. Additionally, users should monitor for pending add-on pods, as VPA may suggest resource requests that exceed available node capacity, and they can customize min/max values for requests and limits of supported add-ons to manage this behavior. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for the Azure Kubernetes Service (AKS) has been updated to standardize terminology related to add-ons. Users can now find clearer instructions on using the `az aks show` command to retrieve the `clientId` of the user-assigned managed identity for the Azure Key Vault Provider, which is essential for managing secrets in Kubernetes Ingress. Additionally, the role assignment for the Key Vault Administrator has been clarified to ensure proper access for the user-assigned managed identity. |
||
|
|
||
|
General 🗑️ Removal Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now clearly states that starting on September 30, 2027, Azure Kubernetes Service (AKS) will no longer support the Open Service Mesh (OSM) add-on, as the upstream OSM project has been retired. Users with clusters utilizing the OSM add-on are advised to migrate to the Istio add-on before the end-of-support date, with specific migration guidance provided in the documentation. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now clarifies that during the cluster creation and bootstrapping stages for network-isolated AKS clusters, no outbound traffic is required. Users will pull images for AKS components and add-ons from a private Azure Container Registry (ACR) connected to the cluster, rather than from the Microsoft Artifact Registry (MAR) over public endpoints. This change enhances the understanding of network isolation capabilities in AKS. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation has been updated to standardize the terminology for the Prometheus add-on, ensuring consistency in the naming convention. Users can now refer to the feature as the "Prometheus add-on" throughout the documentation, which clarifies the process for enabling Prometheus metrics collection from their Kubernetes cluster. |
||
|
|
||
|
Operations ✨ Update Modified: 2026-06-11 19:00 |
||
|
Summary This update includes a fix for broken links related to the Virtual Machine Scale Set terminate notifications, which are prerequisites for AKS node auto-drain. The changes enhance the clarity and accuracy of the documentation. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary The documentation for Azure Kubernetes Service (AKS) has been updated to include detailed descriptions of the two cluster modes: AKS Automatic and AKS Standard. Users can now better understand the differences between these modes, including management features, security defaults, and scaling options, allowing them to choose the most suitable configuration for their needs. Additionally, the article emphasizes the benefits of using AKS Automatic for quick onboarding and reduced operational overhead. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation has been updated to standardize terminology, changing ‘addon’ to ‘add-on’, which improves clarity and consistency. |
||
|
|
||
|
Compute 🆕 New Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now includes a new section on resizing a VMSS node pool in place, allowing users to change the VM size of an existing VMSS-based node pool with a single command using `az aks nodepool update –node-vm-size <new-size>`. This feature simplifies the process by performing a rolling upgrade, which surges new nodes, cordons and drains old nodes, and deletes them, eliminating the need for a manual workflow. Additionally, users are informed about prerequisites and unsupported combinations for the resize operation, ensuring they can effectively manage their node pools. |
||
|
|
||
|
Networking ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary This update standardizes the terminology for the Istio-based service mesh add-on, ensuring consistency and clarity in the documentation regarding compatibility and functionality. |
||
|
|
||
|
General ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now specifies that to install the AKS add-on, users must verify certain items, enhancing the clarity of installation requirements. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-12 11:02 |
||
|
Summary This document introduces AKS end of support notifications, detailing how to receive alerts when a cluster’s Kubernetes version approaches or passes its end of support date. It explains the automatic nature of these notifications and their integration with Azure Resource Graph. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation has been updated to standardize terminology regarding the Azure Monitor managed service for Prometheus, which is crucial for users configuring monitoring solutions in AKS. |
||
|
|
||
|
General ✨ Update Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now specifies to replace `<AZURE_KEYVAULT_CLIENTID>` with the identity client ID of the `azureKeyvaultSecretsProvider` add-on, enhancing clarity for users. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary This document has been revised to provide updated best practices for performance and scaling for large workloads in AKS, emphasizing the recommended use of AKS Automatic as the default for production workloads. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-06-11 22:19 |
||
|
Summary The documentation for AKS has been updated to standardize the terminology for managed add-ons, now consistently referred to as "AKS managed add-ons" instead of "addon." Additionally, the sections detailing breaking changes from Kubernetes versions 1.33.0 and 1.34.0 have been clarified, ensuring users are better informed about the implications of these updates on their AKS deployments. |
||
|
|
||
|
Compute ♻️ Rework Modified: 2026-06-11 19:00 |
||
|
Summary The documentation for the Vertical Pod Autoscaler has been updated to reflect the correct GitHub repository link for the hamster example, now pointing to the vpa-release-0.8 branch. This change ensures users access the appropriate version of the example, which may include important updates or fixes relevant to their implementation. |
||
|
|
||
|
General ✨ Update Modified: 2026-06-12 06:03 |
||
|
Summary This document serves as a reference for health and error codes related to Azure Container Registry, helping users troubleshoot issues effectively. |
||
|
|
||
|
Networking 🆕 New Modified: 2026-06-11 22:19 |
||
|
Summary The document now includes standardized terminology for add-ons and emphasizes the application routing add-on as the recommended method for configuring an Ingress controller in AKS, enhancing clarity for users. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 19:00 |
||
|
Summary The documentation for the Azure Kubernetes Service (AKS) has been updated to recommend starting with AKS Automatic as the default for most production workloads, highlighting its preconfigured best-practice defaults for scaling, security, networking, monitoring, and upgrades. Users can now choose between two cluster modes: AKS Automatic for ease of use and faster deployment, or AKS Standard for more advanced customization options. Additionally, the introduction section has been revised to emphasize AKS fundamentals and common platform areas, enhancing clarity for new users. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-11 22:19 |
||
|
Summary The documentation now includes important notes regarding Azure policy restrictions and resource locks that may affect the management of cluster extensions. Users must ensure that any custom Azure policies blocking the creation or updates to the cluster extensions resource type are updated or exempted, and they should be aware that Azure resource locks can impede management actions. Additionally, a reference to troubleshooting documentation has been added for users needing mitigation details. |
||
|
|
||
|
General 🆕 New Modified: 2026-06-12 06:03 |
||
|
Summary This document has been updated with new author metadata, ensuring proper attribution. The content remains technically relevant and accurate. |
||
|
Full tracker with filters: Azure Container Services Docs Tracker
