Azure Container Services Docs – Weekly Update (2026-01-18 to 2026-01-25)
The most meaningful Azure Kubernetes Service, Container Registry, Application Gateway for Containers, and Fleet Manager documentation changes from the last 7 days. Summaries are AI-filtered to skip trivial edits.
📊 Updates this week: ACR (14), AKS (39), Fleet (4)
|
||
| General ♻️ Rework Modified: 2026-01-22 23:11 | ||
|
Summary The title and content of the article have been updated to clarify the use of Service Principals with Azure Kubernetes Service (AKS). This includes a more detailed explanation of how to create a service principal and delegate permissions for AKS to access required resources. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for setting up permissions and role-based access control (RBAC) in AKS desktop has been updated to clarify user responsibilities and required permissions for both cluster operators and developers. Users can now better understand the specific roles needed for managing projects, including the **Azure Kubernetes Service Cluster User Role**, **Azure Kubernetes Service Namespace User*… |
||
|
|
||
| General 🆕 New Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now clarifies that only Ubuntu 24.04 or Azure Linux 3.0 are compatible for enabling eBPF host routing. Users are directed to refer to the preview documentation for specific instructions on enabling the feature flag when using Ubuntu 24.04. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-24 06:02 | ||
|
Summary The documentation for the Azure Container Registry’s connected registry feature has been updated to clarify that as of August 1, 2025, a monthly fee of $10 will apply for each connected registry deployed, impacting billing for users. Additionally, users can now configure synchronization settings to limit traffic between the cloud and on-premises environments, allowing for more efficient management… |
||
|
|
||
| General 🆕 New Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for the Managed Gateway API has been updated to clarify the installation and upgrade processes for Custom Resource Definitions (CRDs). Users can now expect that when they upgrade their AKS cluster to a new minor version, the CRDs will automatically upgrade to the supported Gateway API bundle version for that Kubernetes version. Additionally, the instructions for installing and un… |
||
|
|
||
| General 🆕 New Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now clarifies that Azure Kubernetes Fleet Manager supports two scopes for staged updates: **Cluster-scoped** using `ClusterStagedUpdateRun` for infrastructure-level changes, and **Namespace-scoped (preview)** using `StagedUpdateRun` for application teams managing rollouts within specific namespaces. Additionally, it emphasizes that `ResourcePlacement` is currently in preview and… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for Azure CNI Overlay networking in Azure Kubernetes Service (AKS) has been updated to clarify the networking model’s features and configurations. Users can now better understand the differences between Azure CNI Overlay and the traditional kubenet model, including details on IP address management, pod communication, and scaling limitations. Additionally, the guidance on configur… |
||
|
|
||
| Operations ♻️ Rework Modified: 2026-01-24 06:02 | ||
|
Summary The documentation for troubleshooting the connected registry extension has been updated to clarify error messages and installation procedures. Users can now find improved guidance on resolving common errors, such as ensuring the extension name is unique and verifying the status of the extension and pod. Additionally, the section on troubleshooting installation failures has been enhanced to include… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now correctly directs users to the updated section on enabling the OIDC Issuer for an existing AKS cluster, specifically referencing the "enable-the-oidc-issuer-on-an-existing-aks-cluster" subsection. This change clarifies the steps users need to take if the OIDC Issuer URL is not enabled, improving the guidance provided in the article. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-21 23:10 | ||
|
Summary The documentation has been updated to reflect the transition from "Trusted Signing" to "Artifact Signing" in GitHub workflows for signing container images. Users can now follow revised instructions to set up an Artifact Signing account and certificate profile, and utilize the corresponding commands and parameters in their workflows, ensuring the authenticity and integrity of their container images… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-22 23:11 | ||
|
Summary The documentation has been updated to clarify the section on service principals in the Kubernetes context. Users can now find relevant information under "Considerations when using a service principal," which replaces the previous "Other considerations" heading, providing more targeted guidance on this topic. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for the Istio support policy has been updated to reflect changes in the expected support timelines and versions for various ASM releases. Specifically, the expected end-of-support date for asm-1-25 has been clarified to January 2026, and the version support for asm-1-27 has been expanded to include version 1.35. Users can now better understand the support lifecycle and version co… |
||
|
|
||
| General 🗑️ Removal Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now specifies that starting on March 17, 2027, AKS will no longer support Ubuntu 20.04, and users must upgrade their node pools to Kubernetes version 1.35 or higher to migrate to a supported Ubuntu version. Additionally, it emphasizes that existing node images will be deleted and security updates will cease, impacting users’ ability to scale their node pools. |
||
|
|
||
| General 🆕 New Modified: 2026-01-21 23:09 | ||
|
Summary The documentation now includes a dedicated section on "Update cluster considerations," which outlines important information users need to keep in mind when updating their AKS clusters. Specifically, it emphasizes the necessity of running the `az aks update –resource-group <resource-group-name> –name <aks-cluster-name> –attach-acr <acr-resource-id>` command if the cluster was using `–attach-acr… |
||
|
|
||
| General 🆕 New Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now reflects that Fleet Manager supports joining up to 200 Kubernetes clusters, an increase from the previous limit of 100, and that member clusters can include both AKS and Arc-enabled Kubernetes clusters, with Arc-enabled support currently in preview. Additionally, the guidance on providing feedback for support of non-AKS clusters has been updated to indicate that this feature… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 23:07 | ||
|
Summary The documentation now clarifies that when running a specific command, users may encounter an error stating, "The object has been modified; please apply your changes to the latest version and try again," which is safe to ignore. This change replaces previous note formatting with direct output examples, making it clearer for users to understand how to handle this error without concern. |
||
|
|
||
| General 🆕 New Modified: 2026-01-21 23:09 | ||
|
Summary The documentation now includes updated information regarding retired Microsoft Defender for Cloud features, specifically referencing Microsoft Defender for Containers. Users can find relevant details about these changes in the newly added sections and include files, which clarify the status of certain features and their implications for container security management. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-21 23:10 | ||
|
Summary The documentation has been updated to remove all references to "Trusted Signing," replacing it with "Artifact Signing" throughout the content. This change clarifies the terminology and ensures consistency, allowing users to better understand the streamlined signing experience offered by Artifact Signing. Additionally, links to tutorials for signing and verifying container images have been updated… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:17 | ||
|
Summary The documentation has been updated to replace all references to "Trusted Signing" with "Artifact Signing." Users can now verify container images in GitHub Actions workflows using Artifact Signing, ensuring authenticity and integrity before using them in builds or deployments. Additionally, the instructions for downloading the relevant root certificates have been updated to reflect this terminology… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:17 | ||
|
Summary The documentation has been updated to replace all references to "Trusted Signing" with "Artifact Signing," reflecting a change in terminology throughout the tutorial. Users can now follow the updated instructions to sign container images in GitHub Actions using Artifact Signing, ensuring the authenticity and integrity of their images in CI/CD pipelines. Additionally, the parameters and roles relat… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-24 06:02 | ||
|
Summary The documentation has been updated to clarify the deployment options for the Connected Registry extension, now titled "Secure Deployment Options for the Connected Registry Extension." Users can now utilize their own certificates (BYOC) or Kubernetes secrets for managing TLS encryption during deployment, providing greater flexibility in securing their connected registry. Additionally, the instructi… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for AKS desktop has been updated to clarify its application-focused experience for deploying and managing workloads on Azure Kubernetes Service (AKS), emphasizing its role in accelerating time to business value. Users can now benefit from simplified application deployment through a guided wizard and automatically generated Kubernetes manifests, as well as enhanced application-cen… |
||
|
|
||
| Operations ♻️ Rework Modified: 2026-01-20 23:07 | ||
|
Summary The AKS monitoring documentation has been updated to include detailed information about the AKS audit policy, which controls event logging and data content based on API request types. Users can now understand the different audit levels—None, Metadata, Request, and RequestResponse—and their implications for logging various operations, including examples of events associated with each level. Additio… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for the `kubectl describe` command has been updated to reflect the correct resource type for describing cluster resource placement statuses. Users should now use `kubectl describe clusterresourceplacementstatuses.v1beta1.placement.kubernetes-fleet.io crp-with-status-reporting -n my-app` to accurately retrieve the status of their cluster resource placements. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for Azure Kubernetes Service (AKS) has been updated to clarify the features and usage of the Free, Standard, and Premium pricing tiers. Users can now find detailed instructions on how to create and update AKS clusters using the Azure CLI, including specific commands for each tier and the requirement to enable Long Term Support when using the Premium tier. Additionally, the articl… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now clarifies that after enabling API Server VNet Integration with the command `az aks update –enable-apiserver-vnet-integration`, users must immediately restart the cluster to ensure the change takes effect due to control plane resource transition. This update emphasizes that the restart is not automated and highlights the importance of this action for all nodes to reliably rec… |
||
|
|
||
| Operations 🗑️ Removal Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now specifies that starting June 17, 2025, AKS will no longer support Ubuntu 18.04, and users must migrate to a supported Ubuntu version to continue receiving security updates and scaling capabilities. Additionally, the default OS SKU for Kubernetes versions 1.35 and above is now Ubuntu 24.04, and users can manually migrate to this version using the `–os-sku Ubuntu2404` command,… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 23:07 | ||
|
Summary The documentation for the KMS data encryption concepts has been updated to clarify that AKS creates and manages only the encryption keys, removing references to Azure Key Vault. This change helps users better understand the specific responsibilities of AKS regarding key management. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 23:07 | ||
|
Summary The documentation now clarifies that when users run specific commands, they may encounter an error stating, "The object has been modified; please apply your changes to the latest version and try again," which is safe to ignore. This change replaces previous note formatting with output formatting for better clarity and consistency in user guidance. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 23:07 | ||
|
Summary The documentation now specifies that users should replace `<RESOURCE_GROUP>` and `<CLUSTER_NAME>` with their AKS cluster’s resource group and name when using the `az aks get-credentials`, `az aks agent-init`, and example commands. This change clarifies the command usage, ensuring users provide the correct parameters for successful execution. |
||
|
|
||
| Security 🆕 New Modified: 2026-01-20 21:28 | ||
|
Summary A new article has been added that provides instructions on migrating to Key Management Service (KMS) infrastructure encryption with platform-managed or customer-managed keys in AKS. This includes prerequisites and important considerations for clusters running Kubernetes version 1.33 or later. |
||
|
|
||
| Networking ♻️ Rework Modified: 2026-01-20 23:07 | ||
|
Summary The documentation for LocalDNS in AKS has been updated to include instructions for using Node Auto-Provisioning (NAP). It clarifies how to enable, disable, and configure LocalDNS with NAP, enhancing the usability of DNS resolution in AKS clusters. |
||
|
|
||
| Networking ✨ Update Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now explains how to expand the pod CIDR space in Azure CNI Overlay AKS clusters, which allows for more flexible network configurations without needing to recreate the AKS cluster. |
||
|
|
||
| Storage 🗑️ Removal Modified: 2026-01-20 21:28 | ||
|
Summary The article on creating persistent volumes with Azure Disks in AKS has been removed, indicating a significant change in how Azure Disks are managed within AKS. This may reflect a shift towards using other storage solutions or updated practices. |
||
|
|
||
| General ✨ Update Modified: 2026-01-21 23:09 | ||
|
Summary [!IMPORTANT] |
||
|
|
||
| General ✨ Update Modified: 2026-01-20 21:28 | ||
|
Summary Learn how to use the Container Storage Interface (CSI) driver to provision volumes in an Azure Kubernetes Service (AKS) cluster. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-24 06:02 | ||
|
Summary The documentation has been updated to clarify the management of access to connected registries in Azure Container Registry (ACR). The title has changed from "Access Control for Connected Registries in ACR" to "Manage access to a connected registry," and the section now emphasizes the creation and management of client and sync tokens, including their specific permissions and usage scenarios. Users… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now clarifies that migrations between AKS Automatic clusters and AKS Standard clusters are supported, with updated guidance on how to perform these migrations. Users can refer to the revised section on updating the SKU of an existing AKS cluster for more detailed instructions. |
||
|
|
||
| Operations 🆕 New Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for the "Max surge" and "Max unavailable" parameters has been updated to reflect new links directing users to the relevant sections in the "upgrade-aks-node-pools-rolling.md" file. Users can now find guidance on customizing node surge upgrades and managing unavailable nodes during upgrades more effectively in the updated locations. |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-22 18:14 | ||
|
Summary The documentation for the `net.netfilter.nf_conntrack_max` and `net.netfilter.nf_conntrack_buckets` parameters has been updated to indicate that their default values are now dynamically calculated based on system memory, providing users with more accurate configurations tailored to their VM sizes. Additionally, the `kernel.threads-max` parameter’s default value is also now dynamically calculated,… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for Azure CNI Overlay in AKS has been updated to clarify the setup process and improve consistency in terminology. Users can now find clearer instructions on creating Azure CNI Overlay AKS clusters, including the use of the `–network-plugin` and `–pod-cidr` parameters, which have been rephrased for better understanding. Additionally, the section on deploying dual-stack AKS clus… |
||
|
|
||
| General 🆕 New Modified: 2026-01-20 21:47 | ||
|
Summary The documentation has been updated to remove all Preview labels from the Artifact Signing section, clarifying that users can now access the full capabilities of Artifact Signing without the preview designation. Additionally, all references to "Trusted Signing" have been changed to "Artifact Signing," ensuring consistency throughout the documentation and allowing users to better understand the curr… |
||
|
|
||
| General ✨ Update Modified: 2026-01-23 23:12 | ||
|
Summary Starting with Kubernetes version 1.29, the sidecar containers feature is enabled by default for AKS, allowing users to utilize Istio native sidecar mode with the Istio add-on. Additionally, beginning with AKS 1.33 and Istio add-on `asm-1-29`, the AKS service mesh add-on will use the native sidecar for the Envoy proxy by default across all clusters, streamlining the setup process for users. Users s… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for using external identity providers with AKS structured authentication has been updated to clarify the identity provider requirements and best practices for security. Users can now find detailed information on supported identity providers, including GitHub and Google OAuth 2.0, and are advised to implement strong claim validation and limit token scope for enhanced security. Add… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-24 06:02 | ||
|
Summary The documentation has been updated to clarify the deployment process for the Connected Registry Arc Extension on Arc-enabled Kubernetes clusters using Azure CLI. Users can now find specific commands for generating a connection string and protected settings JSON file, as well as detailed steps for deploying the extension, including the option to enable automatic upgrades and specify a version durin… |
||
|
|
||
| General 🆕 New Modified: 2026-01-21 06:02 | ||
|
Summary The documentation has been updated to reflect changes in the `gateId` examples for approving gates in Kubernetes Fleet. Users should now reference the new `gateId` format, specifically using **aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e** instead of the previous example. Additionally, the command examples have been updated to align with this new `gateId`, ensuring users have the correct syntax for their… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-21 23:10 | ||
|
Summary The documentation has been updated to replace all references to "Trusted Signing" with "Artifact Signing," reflecting a change in terminology for the certificate management service used in the context of signing container images with Ratify on AKS. Users can now follow updated instructions for signing container images and configuring their environments to utilize Artifact Signing, which offers zer… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-23 18:12 | ||
|
Summary The documentation now clarifies that B series VMs are not supported for system node pools, and Av1 series VMs are not recommended. This change emphasizes the importance of using VM sizes with at least two vCPUs and four GBs of RAM to ensure reliable scheduling of *kube-system* pods and applications. Users should avoid using these VM types to maintain optimal performance in their AKS deployments. |
||
|
|
||
| Compute 🆕 New Modified: 2026-01-20 23:07 | ||
|
Summary The documentation for LocalDNS in AKS has been updated to clarify the configuration options available for enabling and managing LocalDNS. Users can now set the LocalDNS mode to `Required`, which enforces LocalDNS on the node pool if all prerequisites are met, or to `Preferred`, where AKS manages LocalDNS based on the Kubernetes version. Additionally, new details on customizing LocalDNS configurati… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation for deploying applications using the AKS desktop has been updated to clarify the process and improve user guidance. Users can now find detailed steps for adding clusters, creating projects, and deploying applications, including specific instructions for using the Azure CLI extension and managing networking policies. Additionally, the article emphasizes the importance of using AKS… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-24 06:02 | ||
|
Summary The documentation for creating a connected registry in Azure has been updated to clarify that users can now create connected registries with both read-write and read-only functionalities using the Azure CLI and portal. Additionally, users are now required to have an Azure Container Registry in the Premium SKU to utilize the connected registry feature, and they can define synchronization schedules… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-21 23:10 | ||
|
Summary The documentation has been updated to replace references to "Trusted Signing" with "Artifact Signing," reflecting a shift in terminology and functionality. Users can now follow revised instructions for setting up an Artifact Signing account and certificate profile, as well as installing the corresponding Notation plugin. Additionally, commands and environment variables have been updated to align w… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 21:28 | ||
|
Summary The documentation has been updated to clarify the prerequisites for viewing Kubernetes resources in the Azure portal, emphasizing the need for an AKS cluster and the specific requirements for Microsoft Entra integration. Additionally, users are now instructed to configure authorized IP ranges to enable the Kubernetes resource view for existing clusters, enhancing security and access control. The s… |
||
|
|
||
| General 🆕 New Modified: 2026-01-20 23:07 | ||
|
Summary The documentation now includes a new section on verifying KMS configuration after enabling KMS encryption, providing users with a specific Azure CLI command to check their security profile. The output example has been updated to include details about the Azure Key Vault KMS configuration, allowing users to confirm the status of their key management settings more effectively. |
||
|
|
||
| General 🆕 New Modified: 2026-01-20 21:28 | ||
|
Summary The documentation now clarifies that the OpenID Connect (OIDC) issuer is enabled by default for new AKS clusters running Kubernetes version 1.34 and later, eliminating the need to specify the `–enable-oidc-issuer` flag during cluster creation. Additionally, it emphasizes that once the OIDC issuer is enabled on a cluster, it cannot be disabled, and enabling it on existing clusters will require a r… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-24 06:02 | ||
|
Summary The documentation now provides clearer guidance on configuring synchronization schedules for a connected registry using Azure CLI commands. Users can set up their connected registry to sync continuously every minute or to sync daily at midnight, with specific examples and CRON expressions included for each scenario. This enhancement allows cloud administrators to automate updates more effectively,… |
||
|
|
||
| General ♻️ Rework Modified: 2026-01-20 23:07 | ||
|
Summary The documentation now clarifies that when users run the command, they can safely ignore the error message stating, "The object has been modified; please apply your changes to the latest version and try again." This change replaces previous note formatting with a direct output format, making it clearer for users to understand which error can be disregarded during execution. |
||
|
Full tracker with filters: Azure Container Services Docs Tracker
