Azure Container Services Docs – Weekly Update (2026-03-29 to 2026-04-05)
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 (8), AGC (3), AKS (44), Fleet (29)
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation now clarifies that when creating a Fleet Manager with a hub cluster, users can enable additional features such as Kubernetes object propagation and Managed Fleet Namespaces. The reference to Kubernetes object propagation has been updated to point to the correct section on resource placement, ensuring users have accurate information on these capabilities. |
||
|
|
||
|
Security 🆕 New Modified: 2026-04-01 22:08 |
||
|
Summary This article explains how to enable a system-assigned managed identity on a new or existing AKS cluster, get the principal ID of the system-assigned managed identity, and add a role assignment for the system-assigned managed identity. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 11:02 |
||
|
Summary This article introduces Azure Kubernetes Fleet Manager’s intelligent resource placement, addressing the challenges of managing Kubernetes resources across multiple clusters. It outlines the resource placement process, key characteristics, and advantages of using Fleet Manager, providing a detailed guide for platform administrators. |
||
|
|
||
|
Operations ♻️ Rework Modified: 2026-03-30 22:06 |
||
|
Summary The documentation now emphasizes the migration from Virtual Machine Availability Sets to Virtual Machine node pools in Azure Kubernetes Service (AKS), providing clearer guidance on how to perform this migration using a script. Users can now utilize the `az aks update` command with the `–migrate-vmas-to-vms` parameter to facilitate this transition, which also includes an automatic upgrade of Basic-tier load balancers to Standard-tier. Additionally, the article clarifies prerequisites for the migration, such as disabling specific webhooks and Key Management Service during the process. |
||
|
|
||
|
General ✨ Update Modified: 2026-03-31 16:05 |
||
|
Summary The documentation now specifies that all SKUs (Basic, Standard, and Premium) in Azure Container Registry have zone redundancy enabled by default in supported regions, enhancing reliability for users. This update clarifies the capabilities of each SKU while maintaining the same programmatic features and data plane APIs. |
||
|
|
||
|
General 🗑️ Removal Modified: 2026-03-31 16:05 |
||
|
Summary The documentation now clarifies that zone redundancy is enabled by default for all Azure container registries in regions that support availability zones, requiring no special actions from users. Additionally, the `zoneRedundancy` property in the ARM API and Bicep resource definitions is confirmed to be for backward compatibility only, as it no longer controls behavior and is scheduled for deprecation. Users are informed that they do not need to use the `–zone-redundancy` flag in the Azure CLI commands, as zone redundancy is active by default. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 22:12 |
||
|
Summary The documentation has been significantly updated to include Terraform as an option for creating private AKS clusters, enhancing security and network control. It also provides detailed prerequisites and commands for both Azure CLI and Terraform. |
||
|
|
||
|
Security 🆕 New Modified: 2026-04-04 06:02 |
||
|
Summary The Azure Key Vault provider for Secrets Store CSI Driver allows integration of Azure Key Vault as a secret store with AKS clusters. Significant updates include new commands and tips for managing identities and secrets, enhancing security and usability. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-01 17:12 |
||
|
Summary The document has been updated to specify the use of Azure Managed Redis instead of Azure Cache for Redis, providing clearer guidance for users migrating applications from AWS to Azure. |
||
|
|
||
|
Compute ✨ Update Modified: 2026-04-02 22:12 |
||
|
Summary Learn how to migrate your Azure Kubernetes Service (AKS) cluster from cluster autoscaler to node auto-provisioning. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to correct the guidance on workload placement, specifically changing the reference to the correct resource propagation concepts. This ensures users have accurate information for configuring their applications. |
||
|
|
||
|
Compute ♻️ Rework Modified: 2026-03-30 22:06 |
||
|
Summary The documentation for rolling back a node pool version in AKS has been updated to clarify the rollback limitations. Users are now explicitly informed that if cluster autoupgrade is configured, it must be disabled before performing a rollback to prevent automatic upgrades from occurring after the rollback. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-03 22:07 |
||
|
Summary The documentation for the Azure Kubernetes Fleet Manager quickstart has been updated to enhance clarity and usability. Users can now find improved instructions on creating a Fleet Manager and joining member clusters, including clearer descriptions of required permissions and the steps for enabling private hub cluster access. Additionally, screenshots have been refreshed to better illustrate the process within the Azure portal. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in the resource placement concepts, specifically replacing references to "resource propagation" with "resource placement." This change clarifies the terminology used in the context of automated deployments, allowing users to better understand the deployment strategies available in Kubernetes Fleet. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-04-01 17:12 |
||
|
Summary This update reorganizes the Microsoft Entra ID role assignment documentation and includes detailed instructions for assigning roles to managed identities using Azure CLI commands. It emphasizes the importance of assigning the ‘Cognitive Services User’ or ‘Azure AI User’ roles for Azure OpenAI resources. |
||
|
|
||
|
Security 🆕 New Modified: 2026-03-31 22:10 |
||
|
Summary The documentation for managed identities in Azure Kubernetes Service (AKS) has been updated to enhance clarity and usability. Users can now find specific guides for enabling different types of managed identities on new or existing AKS clusters, including system-assigned, user-assigned, and pre-created kubelet managed identities. Additionally, the article title has been capitalized for consistency, and the section on control plane roles has been refined for better readability. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in the resource placement concepts for Kubernetes within Fleet Manager. Users can now access the correct links for both cluster resource placement and the conceptual overview, which have been updated to point to the new resource placement documentation. This ensures that users have the most accurate and relevant information for deploying a hub cluster and managing resource placement across member clusters. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-03-31 22:10 |
||
|
Summary The documentation for the Managed Gateway API Installation for Azure Kubernetes Service (AKS) has been updated to clarify that users can install Custom Resource Definitions (CRDs) independently of any specific Gateway API implementation. Additionally, users must now ensure that only `standard` channel CRDs are installed on their cluster and that the Gateway API bundle version is compatible with their Kubernetes version before enabling the Managed Gateway API. The command examples for creating and updating AKS clusters have also been refined to reflect these changes. |
||
|
|
||
|
Security 🆕 New Modified: 2026-04-01 22:08 |
||
|
Summary This article explains how to enable a user-assigned managed identity on a new or existing AKS cluster, get the principal ID of the user-assigned managed identity, and add a role assignment for the user-assigned managed identity. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in the resource propagation concepts, specifically renaming references to the resource placement concepts. Users can now find relevant information under the updated section for resource placement, enhancing their understanding of how placement drift is managed within Kubernetes Fleet. |
||
|
|
||
|
Storage ♻️ Rework Modified: 2026-04-03 22:07 |
||
|
Summary The documentation now consistently refers to "Azure managed disks" instead of "Azure Managed Disks," ensuring clarity in terminology. Additionally, the section on persistent volume claims has been updated to emphasize that these claims are specified in GiB, while Azure managed disks are billed by SKU for specific sizes, which may impact user understanding of billing and provisioning. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-03-31 16:05 |
||
|
Summary The documentation has been updated to clarify that Azure Container Registry (ACR) now explicitly refers to Microsoft Entra permissions and role assignments. Users can assign ACR roles to various identity types, including Azure Container Apps and Azure Machine Learning identities, to manage permissions effectively. Additionally, the section on scoping role assignments to specific repositories emphasizes the use of Microsoft Entra attribute-based access control (ABAC) for enhanced permission management. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-03-31 16:05 |
||
|
Summary The documentation has been updated to remove references to availability zones and zone redundancy in the context of creating, updating, viewing, listing, and deleting registries. Users will now find that the focus is solely on registry SKUs, which may affect how they understand the capabilities related to registry management. |
||
|
|
||
|
General ✨ Update Modified: 2026-04-02 11:02 |
||
|
Summary This article describes the ResourcePlacement API, which enables fine-grained control over namespace-scoped Kubernetes resources across member clusters using Azure Kubernetes Fleet Manager. It outlines key characteristics, when to use ResourcePlacement, and its components, providing a comprehensive overview for application developers. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 17:51 |
||
|
Summary This document has been updated to clarify the compatibility of Kubernetes versions with Azure Local upgrades, emphasizing the need for supported versions before upgrading. It includes detailed versioning information and upgrade paths. |
||
|
|
||
|
Networking 🆕 New Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in the resource placement concepts for Kubernetes Fleet. Users can now find relevant information under the new section on resource placement, which replaces the previous references to resource propagation. This change enhances clarity on how to manage resource distribution within the fleet. |
||
|
|
||
|
Networking ✨ Update Modified: 2026-04-02 22:12 |
||
|
Summary The documentation now clarifies that the Container Network Service (CNS) is a node local service within Azure Kubernetes Service CNI networking, which allocates, tracks, and programs networking for pods. Additionally, it specifies that CNS sends telemetry (metrics and logs) by default to a Microsoft-managed application insights endpoint, enhancing the troubleshooting process for pod networking IP address assignment issues. Users can expect improved guidance on utilizing CNS for effective network management and troubleshooting. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-03 22:07 |
||
|
Summary The documentation for automating upgrades of Kubernetes and node images using Azure Kubernetes Fleet Manager has been updated to clarify that auto-upgrade profiles can now be created using the `az fleet autoupgradeprofile create` command, with options to disable profiles using the `–disabled` flag. Additionally, users can now specify the `–target-kubernetes-version` parameter to update member clusters to a specific Kubernetes minor version, enhancing control over the upgrade process. The article also emphasizes that auto-upgrade triggered update runs respect planned maintenance windows set at the AKS cluster level. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect a change in the resource propagation concept to resource placement, providing users with clearer guidance on managing resource allocation within Kubernetes Fleet. This change affects the relevant sections that discuss how resources are placed, enhancing the understanding of deployment strategies. Users can now refer to the updated resource placement concepts for more accurate information. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to correct the reference to the resource placement concept, ensuring users are directed to the correct section on resource placement within the Fleet Manager hub cluster. This change clarifies how Kubernetes resource propagation is managed across member clusters, enhancing user understanding of the feature’s functionality. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation for Azure Kubernetes Fleet Manager has been updated to clarify the use of cluster resource placement for managing workloads across multiple clusters, with a specific link correction to the relevant section. Additionally, the article emphasizes the challenges of manual multi-cluster management and outlines the advantages of adopting a hub-and-spoke control plane architecture, which centralizes management and enhances operational efficiency. Users can now better understand how to optimize resource placement and ensure high availability through the updated content. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 17:51 |
||
|
Summary The documentation for Azure Kubernetes Service (AKS) Arc has been updated to clarify the overview of disconnected operations for Azure Local, ensuring users understand the deployment and management of AKS clusters in these environments. Additionally, the required Azure CLI extension versions have been updated, with the `stack-hci-vm` extension now at version 1.11.1, which users must install for compatibility. Users can also find updated links to related articles that provide further guidance on architecture, network requirements, and managing node pools. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect a change in terminology regarding resource propagation, which is now referred to as resource placement. Users should refer to the new section on resource placement for a clearer understanding of the concepts and terminology related to automated deployments. This change may impact how users approach resource management within their Kubernetes deployments. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in terminology, specifically replacing references to "resource propagation" with "resource placement" in the context of Azure Kubernetes Fleet Manager. Users should now refer to the new conceptual overview and resource placement documentation for accurate information on these concepts. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 18:34 |
||
|
Summary The document has been updated to change the topic classification from ‘conceptual’ to ‘how-to’, which enhances its usability for users seeking practical guidance on using WebSockets with the Gateway API in Azure AKS. |
||
|
|
||
|
Compliance ♻️ Rework Modified: 2026-03-31 16:05 |
||
|
Summary The documentation now clarifies that the soft delete policy does not support registries configured for geo-replication or artifact cache, removing the mention of zone redundancy. This change helps users understand the limitations of the soft delete feature more accurately. |
||
|
|
||
|
Security ✨ Update Modified: 2026-04-03 22:07 |
||
|
Summary The document explains the differences between host-based encryption and server-side encryption for Azure Managed Disks, providing essential information for users regarding data security in AKS. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-04-01 06:02 |
||
|
Summary The documentation for the AKS Automatic quickstart has been updated to clarify that users can now create an AKS Automatic cluster using the `–sku` parameter set to `automatic` with the `az aks create` command. Additionally, the instructions for connecting to the cluster have been streamlined, emphasizing the use of the `az aks get-credentials` command to configure `kubectl`, along with updated examples and output formats for better clarity. |
||
|
|
||
|
General 🆕 New Modified: 2026-03-30 17:10 |
||
|
Summary The documentation now specifies that noProxy hosts must be RFC 1123 compliant and that disabling the HTTP Proxy requires a minimum Azure CLI version of 2.85.0. Additionally, the section titles have been updated to remove the "Preview" designation, indicating that the features for disabling the HTTP proxy on existing clusters are now generally available. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-04-01 17:12 |
||
|
Summary The documentation has been updated to include keyless authentication for Azure OpenAI using Microsoft Entra ID. It specifies the necessary role assignments for both client and cluster modes, along with example Azure CLI commands for role assignment. |
||
|
|
||
|
Compute ♻️ Rework Modified: 2026-04-02 17:51 |
||
|
Summary The documentation for Azure Kubernetes Service (AKS) on Azure Local has been updated to include support for the NVIDIA RTX Pro 6000 GPU model, along with its associated VM sizes. Users can now utilize this GPU model with specific SKUs, enhancing their options for GPU resources in AKS. Additionally, the naming convention for NVIDIA has been standardized throughout the document. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-03-30 22:06 |
||
|
Summary The documentation for deploying and configuring an Azure Kubernetes Service (AKS) cluster with Microsoft Entra Workload ID has been updated for clarity and consistency. Users can now find improved instructions for creating a resource group and an AKS cluster, including the use of the `–enable-oidc-issuer` and `–enable-workload-identity` parameters. Additionally, the steps for updating an existing AKS cluster and creating a federated identity credential have been refined to enhance user understanding and execution. |
||
|
|
||
|
Compute 🆕 New Modified: 2026-04-02 22:12 |
||
|
Summary The documentation now includes important considerations for custom node configurations in AKS, emphasizing that custom configurations are reapplied during node image upgrades and preserved during scale-out operations. Users are advised that AKS does not validate custom configuration parameters, and they should ensure that their settings are supported to avoid issues. Additionally, it is recommended to limit permissions for modifying configurations and to separate node pools with custom settings from those without to maintain workload stability. |
||
|
|
||
|
General ✨ Update Modified: 2026-04-02 11:02 |
||
|
Summary This article describes the ClusterResourcePlacement API, which enables resource placement from hub clusters to member clusters using Azure Kubernetes Fleet Manager. It details the API overview, use cases, and the benefits of using Fleet Manager for managing Kubernetes resources across multiple clusters. |
||
|
|
||
|
Operations ♻️ Rework Modified: 2026-04-01 17:12 |
||
|
Summary The documentation now specifies the use of "Azure Managed Redis" instead of "Azure Cache for Redis" when designing stateless applications with AKS. This change clarifies the recommended service for users, ensuring they utilize the appropriate managed service for their application data storage needs. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 17:51 |
||
|
Summary The documentation now includes the Kubernetes versions available in the 2602 release, specifically listing versions 1.31.12, 1.31.13, 1.32.8, 1.32.9, 1.33.4, and 1.33.5. Additionally, it notes that Kubernetes version 1.30 is no longer supported, which may impact users relying on that version for their deployments. |
||
|
|
||
|
Security ✨ Update Modified: 2026-04-04 06:02 |
||
|
Summary The updates clarify the requirements for using the SecretProviderClass in AKS, ensuring users understand the necessary permissions for accessing secrets in Azure Key Vault. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect a change in the reference for resource placement, specifically updating the links from "concepts-resource-propagation" to "concepts-resource-placement." This change clarifies the correct concept users should refer to for understanding resource placement within Kubernetes Fleet. Users can now access more accurate information regarding resource management in their deployments. |
||
|
|
||
|
Networking 🆕 New Modified: 2026-04-02 18:34 |
||
|
Summary The documentation now includes detailed connectivity requirements for the Application Gateway for Containers, specifying both outbound and inbound connectivity needs. Users can reference specific endpoints and ports required for operations, such as Azure ARM API and Entra AD authentication, as well as the backend health and metrics endpoints for troubleshooting. Additionally, the format for frontends has been clarified, indicating they must listen on ports 443 and 80. |
||
|
|
||
|
General 🗑️ Removal Modified: 2026-03-31 16:05 |
||
|
Summary The documentation has been updated to reflect changes in the Azure CLI commands for role assignments related to Azure Container Registry. Users should now use the command `az role assignment create –assignee $CLIENT_ID –scope $ACR_SCOPE –role "acrpull"` instead of including the "acrpush" role, as it has been removed from the examples. Additionally, the "Container Registry Repository Writer" role has also been removed from the commands, simplifying the role assignment process for users. |
||
|
|
||
|
Operations ♻️ Rework Modified: 2026-03-31 22:10 |
||
|
Summary The documentation has been updated to improve clarity in the rollback command for AKS node pools, ensuring users have accurate and actionable instructions. |
||
|
|
||
|
General 🗑️ Removal Modified: 2026-04-02 17:08 |
||
|
Summary The documentation for the quick Kubernetes deployment using the CLI has been updated to remove the MY_DNS_LABEL environment variable, simplifying the deployment process. Users will no longer need to set this variable, which streamlines the setup for creating a Kubernetes cluster. |
||
|
|
||
|
Storage 🆕 New Modified: 2026-03-31 22:10 |
||
|
Summary The documentation now includes updated information regarding the `subscriptionID` parameter, clarifying its requirement alongside the `resourceGroup`. Additionally, users can now enable managed identity for Azure Files persistent volumes by running a new command to set `–enable-smb-oauth true` on the storage account, which is essential for the managed identity scenario. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in the links related to Envelope objects, specifically directing users to the correct sections on resource placement instead of resource propagation. This adjustment clarifies how users can effectively package resources for propagation to member clusters without unintended side effects on the hub cluster. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect the correct link for the "Using ClusterResourcePlacement to deploy cluster-scoped resources" section, now directing users to the appropriate resource placement concepts. This change ensures that users can access the correct information regarding cluster-scoped resource deployment. |
||
|
|
||
|
Security ✨ Update Modified: 2026-04-03 22:07 |
||
|
Summary The documentation now consistently refers to Azure managed disks with correct capitalization. It includes important information on using customer-managed keys for encryption in AKS, ensuring clarity and accuracy. |
||
|
|
||
|
General ✨ Update Modified: 2026-04-02 11:02 |
||
|
Summary This update corrects documentation links to ensure users are directed to the appropriate resources regarding Kubernetes resource placement concepts, enhancing the overall usability of the documentation. |
||
|
|
||
|
General 🆕 New Modified: 2026-03-31 16:05 |
||
|
Summary The documentation for Azure Container Registry has been updated to clarify the introduction of key concepts, emphasizing user control over container content and the features available, such as integrated authentication and geo-replication. Additionally, the instructions for addressing artifacts during push and pull operations have been refined, specifying the format for using digest and clarifying the default behavior when no tag is provided. Users can now better understand how to manage their container images and artifacts effectively within the registry. |
||
|
|
||
|
Storage ✨ Update Modified: 2026-04-03 22:07 |
||
|
Summary The instructions for identifying the node resource group hosting Azure Managed Disks have been clarified, including a consistent use of capitalization for ‘managed disks’. This enhances clarity and consistency in the documentation. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-01 17:12 |
||
|
Summary This update clarifies the use of Azure Managed Redis in examples, replacing previous references to Azure Cache for Redis. This change improves the accuracy of the documentation regarding Azure services. |
||
|
|
||
|
Storage ♻️ Rework Modified: 2026-04-01 06:02 |
||
|
Summary The documentation now specifies that to mount a persistent volume using the NFS protocol, users must have a storage account that is NFS v3 enabled, as it cannot be enabled on existing accounts. Additionally, the command to view the status of the PVC has been updated to use `kubectl get` instead of `kubectl get pvc`, and users are reminded to add their AKS cluster name to the Contributor role on the virtual network and network security group when using NFS protocol. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation now clarifies that when creating a Fleet Manager with a hub cluster, users can enable additional features such as Kubernetes object propagation and Managed Fleet Namespaces. The reference to Kubernetes object propagation has been updated to point to the correct section on resource placement, ensuring users have accurate information for managing their clusters effectively. |
||
|
|
||
|
Security ♻️ Rework Modified: 2026-04-02 17:51 |
||
|
Summary The documentation now clarifies that each secret in the Kubernetes secret store on AKS Edge Essentials is encrypted with a unique Data Encryption Key (DEK), which is generated by the K8s API server and held in memory. Additionally, it emphasizes that while regularly updating secrets is not mandatory, it is recommended to re-write them every 30 days to ensure they are encrypted with the latest Key Encryption Key (KEK). Users can also utilize a command provided in the documentation to re-encrypt their secrets with the latest KEK if desired. |
||
|
|
||
|
General 🆕 New Modified: 2026-03-31 22:10 |
||
|
Summary The documentation for the Azure Kubernetes Service (AKS) has been updated to include a revised table of upcoming and completed API deprecations, providing users with clearer timelines for when specific preview API versions will be deprecated. Notably, new entries have been added for the 2023-10-02-preview and 2023-11-02-preview versions, along with several others extending into 2024, which informs users of the latest deprecation announcements and dates. This change allows users to better plan their migration strategies and ensure continued compatibility with the AKS API. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in the conceptual overviews for tolerations, specifically directing users to the correct section on resource placement instead of resource propagation. This adjustment ensures that users can access the most relevant and accurate information regarding the use of tolerations in Kubernetes fleet management. |
||
|
|
||
|
Networking 🆕 New Modified: 2026-03-31 06:01 |
||
|
Summary The documentation now includes detailed steps for changing a cluster’s existing network policy to Calico, which involves first setting the policy to `none` and then to `calico`. Users can follow the new commands provided to check the current network policy and update it accordingly. Additionally, the section on creating a resource group has been clarified with an example command for better user guidance. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation now clarifies that when Fleet Manager is configured with a hub cluster, users can apply a resource placement to target specific member clusters using label selectors based on service-defined and user-defined labels. Additionally, it specifies that member labels should be modified using the Azure CLI command `az fleet member update` or the REST API, rather than directly on the `MemberCluster` resource. Furthermore, the explanation of tainting a `MemberCluster` with `NoSchedule` has been updated to indicate that it informs the Fleet Manager scheduler about resource allocation restrictions. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect a change in the resource propagation concept to resource placement, specifically in the links provided. Users can now access the correct resource placement documentation, which may enhance their understanding of how resource placement works within Kubernetes Fleet. |
||
|
|
||
|
General ✨ Update Modified: 2026-04-03 22:07 |
||
|
Summary The documentation clarifies that for Kafka deployments on AKS, the Azure Disk CSI driver is used, providing persistent volumes backed by Azure managed disks. This ensures accurate technical guidance for users. |
||
|
|
||
|
General ✨ Update Modified: 2026-04-02 11:02 |
||
|
Summary The documentation now correctly references the "Using ClusterResourcePlacement to deploy cluster-scoped resources" section, updating the link to point to the correct resource placement concept. Additionally, it clarifies that AKS Automated Deployments stages workload definitions on the Fleet Manager hub cluster for propagation to member clusters, emphasizing the single AKS cluster support. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 11:02 |
||
|
Summary The documentation now specifies that when creating a Fleet Manager with a hub cluster, users can utilize features such as Kubernetes object propagation, which has been updated to refer to the correct section on resource placement. This change clarifies the capabilities available to users managing AKS and Arc-enabled clusters within a Fleet Manager setup. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation has been updated to reflect changes in the resource propagation concepts, specifically replacing references to "resource propagation" with "resource placement." This change clarifies the terminology used in the documentation, ensuring users have accurate information regarding resource placement in Kubernetes Fleet. |
||
|
|
||
|
Security 🆕 New Modified: 2026-04-01 22:08 |
||
|
Summary This article explains how to enable a pre-created kubelet managed identity on a new or existing AKS cluster, get the properties of the kubelet managed identity, and add a role assignment for the kubelet managed identity. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-01 22:08 |
||
|
Summary The document has been updated to fix formatting issues related to limitations for the application routing Gateway API. This includes improved clarity in the command examples and notes regarding the deletion of Istio custom resources. |
||
|
|
||
|
Storage ✨ Update Modified: 2026-04-03 22:07 |
||
|
Summary The updates include critical information about zone-redundant storage (ZRS) for AKS clusters, enhancing the understanding of storage options and their implications for data resilience. |
||
|
|
||
|
Networking ♻️ Rework Modified: 2026-04-02 17:51 |
||
|
Summary The documentation has been updated to clarify that the Azure Arc gateway simplifies network configuration specifically for AKS on Azure Local clusters. Users are now instructed to complete prerequisites for creating AKS clusters on Azure Local before using the Arc gateway, and they can find a complete list of required URLs and endpoints that must be allowed through their enterprise firewall. Additionally, the commands for creating, updating, and disabling the AKS Arc gateway have been retained, ensuring users can manage their configurations effectively. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation now correctly references the Fleet Manager Cluster Resource Placement (CRP) as "concepts-resource-placement.md" instead of the previous incorrect link to "concepts-resource-propagation.md." This change clarifies the resource placement process for Managed Fleet Namespaces, ensuring users have accurate information on how namespaces are propagated to member clusters. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 18:34 |
||
|
Summary The topic classification for the WebSockets documentation has been updated from ‘conceptual’ to ‘concept-article’, improving the categorization and potentially aiding users in finding relevant content more effectively. |
||
|
|
||
|
General 🆕 New Modified: 2026-04-02 17:51 |
||
|
Summary The documentation now includes two new known issues for Azure Kubernetes Service (AKS): one regarding clusters with Azure Policy or Gatekeeper becoming unhealthy after an upgrade, and another about cluster creation failures following an Azure Local update from version 2510. Users can refer to these updated sections for guidance on troubleshooting these specific issues. |
||
|
|
||
|
General 🗑️ Removal Modified: 2026-03-31 22:10 |
||
|
Summary This article has been removed, which previously provided instructions on using managed identities in AKS. The content has likely been consolidated into other articles for better clarity and organization. |
||
|
|
||
|
Storage ✨ Update Modified: 2026-03-31 16:05 |
||
|
Summary The documentation now states that zone redundancy is enabled by default in select Azure regions for Azure container registries, enhancing resilience and high availability. Users can benefit from automatic replication of their registry across a minimum of three separate zones without needing to enable this feature manually. |
||
|
|
||
|
Storage 🗑️ Removal Modified: 2026-04-01 06:02 |
||
|
Summary The documentation now clarifies that starting with Kubernetes version 1.26, in-tree persistent volume types `kubernetes.io/azure-disk` and `kubernetes.io/azure-file` are deprecated and no longer supported. Users can enable or disable the Azure Disks, Azure Files, and Azure Blob storage CSI drivers on existing clusters using the `az aks update` command with the respective `–enable` or `–disable` parameters, along with the option to enable or disable the snapshot controller simultaneously. |
||
|
|
||
|
General ♻️ Rework Modified: 2026-04-02 11:02 |
||
|
Summary The documentation for intelligent resource placement has been updated to reflect changes in the resource placement concepts, specifically updating references from "resource propagation" to "resource placement." Users can now find accurate links to the cluster-scoped and namespace-scoped resource placement documentation, which will help them better understand how to deploy workloads without encapsulating resources. Additionally, the weight calculation formula for cluster resource placement has been clarified with updated references. |
||
|
|
||
|
Storage ♻️ Rework Modified: 2026-04-03 22:07 |
||
|
Summary The documentation has been updated to clarify the syntax for defining PersistentVolume settings for databases using Azure Managed Disks, emphasizing the benefits of keeping data and WAL on the same volume for better throughput. This change enhances user understanding of storage configurations. |
||
|
Full tracker with filters: Azure Container Services Docs Tracker
