Azure Container Services Docs – Weekly Update (2026-10-25 to 2026-11-01)
The most meaningful Azure Kubernetes Service, AKS Application Network, Azure Arc-enabled Kubernetes, 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 (2), AKS (17), AKS Arc (2), AKS Automatic (1), AKS Support (29), App Net (1), Arc K8s (9)
|
|
|
General ✨ Update Detected: 2026-10-31 00:15 UTC |
|
|
Summary The article has been updated to include additional details about Application Network versions, their support lifecycle, and compatibility with Azure Kubernetes Service (AKS) versions. New information includes end-of-life estimates, fully managed release channels, and clarifications on version management. The table format has also been enhanced to provide clearer information on retired versions and their support status. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary This article has been revised to specify that the troubleshooting steps apply to Azure Kubernetes Service (AKS). It also includes minor clarifications to improve the overall understanding of the resource viewer access issues. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary This article provides guidance on troubleshooting access issues to the AKS API server when authorized IP address ranges block connections. It emphasizes the importance of correctly setting the authorized IP ranges during cluster creation or updates. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary The article discusses troubleshooting DNS resolution failures from inside a pod in AKS. It includes updated prerequisites and clarifications on how upstream DNS servers are determined based on the worker node’s resolv.conf file. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary The article outlines common causes for a missing AKS config file when connecting to a cluster, including solutions for saving credentials and ensuring the config file is in the correct directory. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary The article assists in troubleshooting image pull errors from Azure Container Registry to AKS, detailing common issues and providing solutions for authentication and network connectivity problems. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary This article has been updated to clarify the troubleshooting steps for outbound connections from an AKS cluster. It includes new sections on prerequisites and advanced diagnostics, enhancing the guidance on identifying and resolving connectivity issues. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary This article has been updated to enhance clarity on troubleshooting client IP access issues to the AKS API server. It includes clearer instructions and emphasizes the importance of checking authorized IP ranges, improving the user experience. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary The article now provides a more structured workflow for troubleshooting DNS resolution problems in AKS. It emphasizes the importance of prerequisites and clarifies the troubleshooting process, making it easier for users to diagnose and fix DNS failures. |
|
|
|
|
|
General ♻️ Rework Detected: 2026-10-30 18:10 UTC |
|
|
Summary The article has been significantly expanded to include detailed steps for migrating from AKS Standard to AKS Automatic clusters with managed system node pools. It outlines prerequisites, migration requirements, and verification steps, providing comprehensive guidance for users. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-30 18:10 UTC |
|
|
Summary This article helps troubleshoot tunnel connectivity issues in AKS, detailing symptoms and causes related to excessive API server traffic due to Grafana Alloy log collection. It provides solutions to configure Grafana Alloy for better performance. |
|
|
|
|
|
General ♻️ Rework Detected: 2026-10-30 00:17 UTC |
|
|
Summary The article now includes instructions for deploying a sample Ray workload to confirm that the KubeRay operator manages Ray resources as expected. It provides detailed steps for creating a namespace, deploying a RayCluster, and submitting a RayJob, enhancing the practical guidance for users. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-30 00:17 UTC |
|
|
Summary The article has been updated with new release notes for the Azure Policy Extension, including security improvements and version compatibility details. This enhances the documentation’s relevance for users managing Azure Arc-enabled Kubernetes clusters. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-30 00:17 UTC |
|
|
Summary The article now specifies that the AKS-managed `managedNATGateway` outbound type supports and defaults to StandardV2 NAT gateway in eligible regions, providing clearer guidance on dual-stack networking configurations. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-29 18:11 UTC |
|
|
Summary The article has been updated to clarify the management of upgrades for AKS enabled by Azure Arc, specifying options for both hyperconverged and bare-metal deployments. It also emphasizes the importance of secure defaults and SSH access management, providing additional guidance on physical protections for edge clusters. |
|
|
|
|
|
Operations ♻️ Rework Detected: 2026-10-29 18:11 UTC |
|
|
Summary The troubleshooting guide for the OutboundConnFailVMExtensionError has been significantly enhanced with detailed steps for identifying and resolving connectivity issues. New sections include prerequisites for troubleshooting, expanded error message explanations, and improved clarity on testing outbound connectivity, making it more user-friendly. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-29 18:11 UTC |
|
|
Summary The release notes for the AKV Secret Store extension have been updated to include new version details, specifically version 1.6.1, which addresses vulnerabilities and updates trusted root certificate authorities. This ensures users are informed about the latest security enhancements. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-29 18:11 UTC |
|
|
Summary This article now emphasizes creating extra protection for management and data traffic in Azure Arc-enabled Kubernetes. It includes updated guidance on IP address planning for both hyperconverged and bare-metal deployments. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-29 18:11 UTC |
|
|
Summary Updates to the guidance on securing data in Azure Arc-enabled Kubernetes include clarifications on encryption practices for AKS enabled by Azure Arc on Azure Local hyperconverged deployments. The article now emphasizes the importance of protecting sensitive workload data and provides clearer recovery planning advice. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-29 18:11 UTC |
|
|
Summary The security book for Azure Arc-enabled Kubernetes and AKS has been updated to clarify deployment options and enhance guidance on security workflows. It now includes specific references to deployment options on Azure Local and K3s, improving the overall clarity and usability of the content. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-29 18:11 UTC |
|
|
Summary The article has been revised to clarify the integration of Kubernetes with Microsoft Entra ID for user account management and authorization policies. It emphasizes the importance of a least privilege approach for user roles and provides guidance on downloading an admin client certificate. |
|
|
|
|
|
Operations ♻️ Rework Detected: 2026-10-29 18:11 UTC |
|
|
Summary This article has been significantly updated to enhance troubleshooting guidance for managed KubeRay extension errors in Azure Kubernetes Service (AKS). Key changes include detailed procedures for diagnosing installation issues, managing CRDs, and ensuring successful operator transitions. New commands and warnings have been added to improve user understanding and mitigate risks during the troubleshooting process. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-29 12:12 UTC |
|
|
Summary The content was revised to clarify that cluster creation and lifecycle operations do not require outbound traffic from network isolated clusters. It also emphasizes the need for outbound access only when enabling specific features or add-ons, improving the guidance on network isolation. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-29 12:12 UTC |
|
|
Summary The article was updated to clarify that the endpoints `md-*.blob.storage.azure.net` and `umsa*.blob.core.windows.net` are not required for AKS egress. It also provides additional details on the fallback mechanism for the Azure Linux VM Agent if these endpoints are blocked, enhancing user understanding of network dependencies. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-29 06:13 UTC |
|
|
Summary The ResourceId in the quickstart guide for connecting an existing Kubernetes cluster to Azure Arc has been updated to reflect a new subscription ID. This change is important for users following the tutorial to ensure they are using the correct resource path. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-28 18:11 UTC |
|
|
Summary Updated the policy definition for restricting external private endpoints in Azure Container Registry. The new version (1.1.0) includes a link to the updated policy details and emphasizes the importance of preserving enclave boundaries to reduce data exposure risk. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-28 18:11 UTC |
|
|
Summary Enhanced the built-in policy definitions for Azure Arc-enabled Kubernetes. The updates include new policies for restricting pod access to host networks and ports, improving security compliance with Pod Security Standards, and preventing the use of ContainerAdministrator for Windows containers. |
|
|
|
|
|
Compliance ✨ Update Detected: 2026-10-28 06:12 UTC |
|
|
Summary Modified the built-in policy definitions for Azure Kubernetes Service, including updates to deployment safeguards and best practices. This provides clearer guidance for users implementing policies. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 06:12 UTC |
|
|
Summary Updated the scheduling syntax for node auto-provisioning disruptions, clarifying the use of cron job syntax and providing additional details on budget activation. This enhances user understanding of disruption policies. |
|
|
|
|
|
Security ♻️ Rework Detected: 2026-10-28 06:12 UTC |
|
|
Summary Updated the Azure Policy Regulatory Compliance controls for AKS, reflecting changes in access control policies and ensuring compliance with the latest standards. This is crucial for maintaining security posture. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation for troubleshooting AKS pod scheduler errors has been updated to clarify the causes and solutions for common issues that prevent pods from running. Users can now find more detailed steps for resolving volume node affinity conflicts and insufficient CPU issues, including specific commands to scale the node pool. Additionally, the section on untolerated taints has been enhanced to emphasize the need for matching tolerations in pod specifications. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The article has been revised to improve clarity on factors affecting container image pull performance in AKS, providing users with actionable insights. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now clarifies that when using static private IP allocation for Azure Container Registry, adding geo-replicas or enabling regional endpoints can fail if the required member-to-IP mappings are not configured. Users are advised to create the private endpoint only after all geo-replicas are established to ensure proper IP configuration, and to use dynamic IP allocation if they plan to add geo-replicas or enable regional endpoints later, as this will automate the necessary member mappings. |
|
|
|
|
|
Compute ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now includes a new section outlining prerequisites for troubleshooting memory saturation in AKS clusters, detailing commands such as `kubectl top node`, `kubectl get pods`, and `kubectl describe node` for gathering memory usage data. Additionally, the guidance on using memory requests and limits has been clarified to emphasize the importance of setting these values appropriately to avoid memory pressure on nodes. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The article now provides guidance on identifying containers causing high disk I/O latency in AKS clusters, enhancing troubleshooting capabilities for performance issues. |
|
|
|
|
|
Compute ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation has been updated to clarify the troubleshooting process for **Node Not Ready** failures in Azure Kubernetes Service (AKS) clusters. Users can now better understand the root causes of these failures and implement effective resolutions to prevent repeat outages. Additionally, the phrasing has been adjusted for clarity regarding the importance of service tier payments. |
|
|
|
|
|
Compute ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now emphasizes troubleshooting the **Node Not Ready** state in Azure Kubernetes Service (AKS) clusters due to expired certificates, providing clearer guidance on identifying and rotating these certificates. Additionally, the prerequisites for troubleshooting have been specified, enhancing user understanding of necessary steps before proceeding with commands like `az vmss run-command invoke` and `az vm run-command invoke`. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The article has been updated to clarify troubleshooting steps for AKS nodes that unexpectedly change to Not Ready status, improving guidance for users. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary This article has been enhanced to provide a clearer understanding of common node auto-repair errors in AKS, including a table of error codes and best practices for monitoring and responding to errors. |
|
|
|
|
|
Compliance ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The support policy for the Istio-based service mesh add-on for Azure Kubernetes Service has been updated with revised expected end-of-life dates for specific versions. Users can now expect the end-of-life for asm-1-29 to be around December 2026, and for asm-1-31 around March 2027, allowing for better planning and management of their service mesh deployments. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The article has been updated to help troubleshoot custom script extension errors that prevent AKS nodes from provisioning, providing clearer steps for identifying and resolving issues. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now includes a note about the limitations of using a separate NGINX ingress controller in multi-tenant clusters, emphasizing security considerations. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now specifies that the parameters `defaultTrafficPolicy`, `serviceEntryVisibility`, `zoneAwareLbSetting`, and `connectionSettings` are configurable starting with asm-1-31. This allows users to customize these settings for the Istio-based service mesh add-on in Azure Kubernetes Service, enhancing their control over traffic management and service visibility. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now includes a new section on multi-tenant clusters, highlighting that the managed NGINX Ingress controller does not provide isolation at the namespace level and should not be used as a security boundary in shared clusters. Users are informed about the implications of using Ingress objects across namespaces, including shared configurations and access to Secrets, along with recommended practices to mitigate risks in multi-tenant environments. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now provides clearer guidance on troubleshooting issues related to the Azure Kubernetes Service (AKS) load balancer health probe mode, including detailed steps for checking configurations and logs. Users can better understand the implications of using the Shared and ServiceNodePort modes, as well as the necessary commands to enable these features and verify their configurations. Additionally, the article emphasizes the requirement for the Azure Standard Load Balancer SKU for the health probe mode feature to function correctly. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary Clarified the indicators for interpreting pod age and restart behavior, enhancing the troubleshooting guidance for users. This includes details on reviewing Kubernetes audit logs. |
|
|
|
|
|
Operations ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The article has been updated to clarify the use of Pressure Stall Information (PSI) metrics for troubleshooting CPU pressure in AKS clusters. It emphasizes the importance of understanding CPU pressure as a more accurate indicator of resource contention than traditional metrics. |
|
|
|
|
|
Compute ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation for troubleshooting "Node Not Ready" issues in Azure Kubernetes Service has been updated to enhance clarity and usability. It now explicitly states that the article helps users recover their cluster nodes and provides detailed explanations of common error messages for both Windows and Linux nodes. Additionally, the section titles have been revised for better alignment with troubleshooting practices, improving the overall user experience. |
|
|
|
|
|
Operations ♻️ Rework Detected: 2026-10-28 00:16 UTC |
|
|
Summary This article has been revised to improve clarity on troubleshooting OOMKilled errors in AKS clusters, including identifying root causes and applying solutions to prevent memory-related pod restarts. |
|
|
|
|
|
Storage ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation now provides clearer guidance on troubleshooting high memory consumption in disk-intensive applications on Kubernetes pods, specifically identifying Linux kernel caching as a potential cause and offering solutions to reduce memory pressure. Additionally, the steps for inspecting pod memory consumption and dropping the Linux kernel cache have been refined for better clarity, ensuring users can effectively manage memory resources in their Kubernetes environments. |
|
|
|
|
|
Compute ✨ Update Detected: 2026-10-28 00:16 UTC |
|
|
Summary The documentation has been updated to enhance clarity on troubleshooting high CPU usage in Azure Kubernetes Service (AKS) clusters. Users can now follow a more structured approach to identify high CPU-consuming nodes and containers, with clearer steps for utilizing the Container Insights feature in the Azure portal. Additionally, best practices for managing CPU usage have been refined, providing users with actionable guidance to improve performance and reliability. |
|
|
|
|
|
Security 🆕 New Detected: 2026-10-27 20:30 UTC |
|
|
Summary New documentation page: Troubleshoot cluster-level FIPS errors in AKS (preview) – Azure | Microsoft Learn. Review the published article and captured content diff. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-27 18:10 UTC |
|
|
Summary The documentation now includes instructions for associating an existing capacity reservation group (CRG) with both new clusters and new system node pools in Azure Kubernetes Service (AKS). Users can create a cluster with a CRG by using the `az aks create` command with the `–assign-identity` and `–crg-id` flags, and they can also add a CRG to a new system node pool using the `az aks nodepool add` command with the `–mode System` and `–crg-id` flags. Additionally, guidance has been clarified for managing non-zonal system node pools without needing to scale them to zero. |
|
|
|
|
|
Operations ♻️ Rework Detected: 2026-10-27 18:10 UTC |
|
|
Summary The documentation now provides enhanced troubleshooting guidance for common issues when running or scaling large Azure Kubernetes Service (AKS) clusters, specifically addressing quota, networking, scaling, and upgrade problems. Users can now better understand how to resolve "InsufficientSubnetSize" errors and are advised to use Azure CLI for scaling operations, with clear instructions on managing node pools and verifying regional quotas. Additionally, the article emphasizes the importance of planning for subnet capacity and using the Managed NAT Gateway for improved scalability in large clusters. |
|
|
|
|
|
Networking ✨ Update Detected: 2026-10-27 00:19 UTC |
|
|
Summary Added a section on dual-stack networking considerations for Node Auto-Provisioning (NAP) in AKS, including prerequisites and limitations for IPv4/IPv6 dual-stack cluster networking. This enhances understanding of networking configurations for users implementing NAP. |
|
|
|
|
|
General ♻️ Rework Detected: 2026-10-27 00:19 UTC |
|
|
Summary Introduced detailed configurations for Azure Container Linux and Windows Server images in AKS, including Trusted Launch settings and limitations. This provides critical information for users configuring node pools with specific OS requirements. |
|
|
|
|
|
Compute ♻️ Rework Detected: 2026-10-27 00:19 UTC |
|
|
Summary Updated the procedure for creating an AKS-managed GPU node pool, emphasizing the use of `mode: Driver` and `nvidia.managementMode: Managed` in the `spec.gpu` field. This change clarifies the setup for users looking to utilize managed GPU experiences in AKS. |
|
|
|
|
|
Security 🆕 New Detected: 2026-10-25 12:12 UTC |
|
|
Summary Added a comprehensive guide on enabling Federal Information Processing Standard (FIPS) for AKS clusters, detailing prerequisites, limitations, and the implications of FIPS mode on node pools and AKS-managed components. |
|
|
|
|
|
Security ✨ Update Detected: 2026-10-25 12:12 UTC |
|
|
Summary Clarified the process for updating existing Linux node pools to enable or disable FIPS, specifying the transition between FIPS and non-FIPS images and the reimage requirement, which may extend the update time. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-25 12:12 UTC |
|
|
Summary Introduced new Kubernetes versions included in the 2610 release for AKS Hybrid and Edge, providing users with updated version information for better planning and deployment. |
|
|
|
|
|
General ✨ Update Detected: 2026-10-25 12:12 UTC |
|
|
Summary Updated the supported Kubernetes versions for AKS Hybrid and Edge, including new version details and emphasizing the importance of sequential upgrade paths for clusters. |
|
|
Full tracker with filters: Azure Container Services Docs Tracker