The documentation has been updated to reflect the use of version 1.11.3 of the Helm chart for deploying the Application Gateway for Containers. Users should now reference this updated version in their commands to ensure compatibility and access to the latest features and fixes.

The document has been updated to include new information regarding managing node pools in AKS, enhancing the guidance provided to users.

This document has been updated to reflect the latest status of Azure Files features, including the removal of preview labels and the addition of managed identity support for Azure Files in AKS starting with version 1.35.0.

The Prepared Image Specification (PIS) feature in Azure Kubernetes Service (AKS) allows users to create preconfigured node images that include required container images and customizations. This reduces provisioning latency and accelerates scale-out operations, particularly beneficial for performance-sensitive workloads. The article details how PIS works, its common use cases, and compares it with related AKS features.

This article has been updated to include best practices for MLOps in AKS, emphasizing Infrastructure as Code, containerization, model management, automation, scalability, and security. It provides a comprehensive overview of considerations for deploying and managing machine learning models in production environments.

Updated the requirements for AKS address ranges, specifying that they must not overlap certain reserved IP ranges. This change clarifies the rules for configuring Kubernetes services, pods, and cluster virtual networks in AKS, enhancing the documentation’s technical accuracy.

The overview document has undergone several modifications, including updates to links and content structure, enhancing clarity and accessibility for users. This includes correcting URLs to ensure they point to the correct resources.

The documentation for IP address planning in AKS enabled by Azure Arc has been updated to correct links to the AKS networking concepts and requirements. Users can now access the correct resource for understanding the networking requirements necessary for deploying AKS in production, ensuring they have the most accurate information for effective IP address planning.

The documentation has been updated to include detailed instructions on creating and managing cross-cluster networking in Azure Kubernetes Service (AKS). This includes commands for applying network profiles, managing member clusters, and validating network connections. New examples and notes on best practices for using Cilium with AKS have also been added.

The documentation for Azure Kubernetes Service (AKS) has been updated to include detailed instructions on enabling Trusted Launch features such as Secure Boot and vTPM. It specifies the requirements for using these features, including the need for specific Bicep and ARM template configurations. Additionally, it clarifies that the AzureRM Terraform provider does not support Trusted Launch, and provides examples for deploying and verifying node pools with these security features enabled.

The documentation has been updated to clarify that users must ensure logical network IP addresses can connect to all management IP pool addresses on the required ports, with a detailed list of ports now referenced in the updated section on network requirements. Additionally, users are reminded to verify that outbound internet access is available for logical network IP addresses and that necessary AKS URLs are accessible from the Arc VM logical network.

The documentation now emphasizes the use of a single node pool for each availability zone when implementing the cluster autoscaler, recommending the `–balance-similar-node-groups` parameter to maintain node distribution during scaling operations. Additionally, users can utilize automatic zone placement with the `–zones auto` option, allowing AKS to dynamically select zones based on capacity. The guidance for managing clusters with both long-running and bursty workloads has been clarified, suggesting the separation of these workloads into distinct node pools using affinity rules or expanders.

Documented limitations of AKS stop/start operations with KAITO Workspaces, highlighting potential issues such as node pool reconciliation conflicts and provisioning failures. This update provides critical information for users managing AKS clusters with KAITO Workspaces.

Significant updates have been made to the system requirements for AKS on bare metal, including a reorganization of the instructions for registering resource providers. This improves the clarity and usability of the documentation for users setting up AKS on bare metal.

The documentation now includes a new tip highlighting the option for users to utilize **automatic zone placement** (`–zones auto`) when creating or updating a node pool in AKS, allowing for easier zone management without manual selection. Additionally, a link to the detailed section on automatic zone placement for node pools has been added, providing users with more comprehensive guidance on this feature.

The documentation now clarifies that if users have a firewall isolating the management network from logical networks, they must ensure the required ports are open for the management network to reach AKS Arc VMs. Additionally, the links to the network requirements and networking prerequisites for AKS on Azure Local have been updated to direct users to the correct resources.

This article details the core concepts and architectural models for multi-tenancy on Azure Kubernetes Service (AKS). It explains the rationale for multi-tenancy, the differences between soft and hard multi-tenancy, and the isolation spectrum, which includes namespace isolation, node pool isolation, and cluster-per-tenant models.

The documentation for starting and stopping AKS clusters has been updated to clarify that for private link-based AKS clusters, the API server private endpoint is recreated upon starting the cluster. This change emphasizes the importance of understanding how the private endpoint is managed in relation to node pools.

This document provides best practices for implementing multi-tenancy in Azure Kubernetes Service (AKS), including namespace isolation, Kubernetes RBAC with Microsoft Entra ID, ACNS Cilium network policies, resource quotas, pod security admission, node pool isolation, and Azure Monitor. It outlines prerequisites, baseline cluster creation, and various strategies for managing tenant workloads effectively.

The documentation for retrieving kubelet logs has been updated to reflect a new link to the "Get kubelet logs" section, now directing users to "aks-get-kubelet-logs.md" instead of the previous "get-kubelet-logs.md." This change ensures that users access the most current and relevant information for collecting kubelet logs in AKS Arc environments.

This document outlines recommendations for achieving zone resiliency in AKS, including the use of automatic zone placement to enhance application availability and reduce deployment failures. It emphasizes the importance of understanding zone configurations and their impact on workload performance.

This update clarifies the resolution of an issue related to AKS on Azure Local, providing users with the correct version reference and improving the known issues section for better guidance.

The documentation now correctly references known issues related to AKS enabled by Azure Arc, improving the accuracy of the troubleshooting information provided.

The document provides best practices for performance and scaling in AKS, emphasizing the use of availability zones to enhance application availability. It includes recommendations for managing workloads and optimizing resource allocation during scaling operations.

The documentation now includes important notes regarding the placement of the API server private endpoint in the subnet used by the first node pool. This update is crucial for understanding the implications of changing node pool configurations on the private endpoint.

The documentation for the AKS Arc diagnostic checker has been updated to clarify the networking concepts necessary for creating an AKS cluster, specifically changing the reference to the networking requirements document. Additionally, the descriptions for the diagnostic tests, including the cloud-agent-connectivity-test, gateway-icmp-ping-test, and http-connectivity-required-url-test, have been enhanced to provide clearer guidance on potential causes for failure and mitigation recommendations. Users can now better understand how to troubleshoot connectivity issues related to their AKS clusters.

This document provides a comprehensive guide on creating and managing a Prepared Image Specification (PIS) in Azure Kubernetes Service (AKS). It includes prerequisites, step-by-step instructions, and best practices for using PIS to optimize node provisioning and scaling, thereby improving application performance.

This document introduces automatic zone placement in Azure Kubernetes Service (AKS), allowing AKS to dynamically select availability zones for node pools. It explains how to create or update node pools using the `–zones auto` option, which helps improve resilience and reduce deployment failures by automatically managing zone allocations.

The updated documentation on AKS Node Auto-Provisioning includes security settings for host-level encryption and support for customer-managed keys and disk encryption sets. It emphasizes the importance of proper role-based access control (RBAC) for managing these features effectively.

This update includes significant changes to the commands for creating AKS clusters using Azure CLI, ensuring users have the latest syntax and options available. It also corrects reviewer information and improves clarity in the documentation.

A new guide has been added for migrating legacy .NET Framework and Windows IIS applications to AKS. It covers assessment, planning, and execution, providing practical pathways for containerization and refactoring to modern frameworks.

This update improves the known issues section for AKS enabled by Azure Arc, providing clearer links and references to help users troubleshoot effectively.

The release notes for the ALB Controller have been updated to include new features and security patches, providing users with the latest information on improvements and fixes in the Azure Kubernetes Service environment.

The document now includes a clear intent statement for IT professionals on how to obtain kubelet logs for troubleshooting in Azure Kubernetes Service enabled by Arc. This enhances the usability of the documentation.

The document has been updated to improve clarity on telemetry pod resources, including better references to known issues and troubleshooting steps.

The documentation now emphasizes the importance of adding users to the Microsoft Entra group to access the AKS cluster enabled by Azure Arc using `kubectl`. Additionally, the link to the prerequisites for AKS on Azure Local has been updated to point to the correct resource. Users should ensure they follow these updated instructions to avoid access issues.

The documentation for the service mesh integration has been updated with a new version number for the command, reflecting the latest changes in the Azure Application Gateway. This ensures users have the most current information for implementation.

The documentation has been updated to reflect the renaming of the feature flag from `AKSNodeCustomizationPreview` to `CustomNodeConfigPreview`, which is required for using the preview `kubeReserved` and `hardEvictionThreshold` kubelet settings on Linux node pools. Users should now register the `CustomNodeConfigPreview` feature flag using the `az feature register` command to access these settings. Additionally, the prerequisites section has been updated to ensure clarity on the new feature flag requirement.

This update emphasizes the importance of ensuring sufficient usable IP addresses in logical networks to prevent deployment failures, enhancing the guidance for network planning.

The documentation has been updated to correct the links related to the prerequisites for creating AKS clusters on Azure Local. Users should now refer to the updated section for accurate information on network system requirements, ensuring they have the correct guidance when using Azure Arc gateway with AKS on Azure Local.

Fixed links related to AKS Arc Hyperconverged and disaggregated configurations, ensuring that users have access to the correct resources. This update improves the usability and accuracy of the troubleshooting documentation.

This article has been updated to clarify the deployment process for the Inference Gateway, including links to the Gateway API Inference Extension guides. It provides essential information for developers looking to implement inference capabilities in their applications.

The documentation has been updated to correct links related to the AKS on Azure Local prerequisites, specifically changing references from "aks-hci-network-system-requirements.md" to "network-system-requirements.md." This change ensures users are directed to the correct resource for understanding the network system requirements for AKS on Azure.

The document has been updated to reflect new supported Kubernetes versions for Azure Kubernetes Service (AKS) on Azure Arc, including changes to the release dates and authorship. Notably, the supported versions have been updated to include releases 2604 through 2607, and the last reviewed date has been changed to July 23, 2026.

File: articles/aks/quickstart-event-grid.md Subjects: – Fix resource group name in AKS creation command – Merge pull request #3564 from MicrosoftDocs/main – Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-aks-docs (branch main) (#3562) Patch excerpt: -az aks create –resource-group yResourceGroup –name MyAKS –location eastus –node-count 1 –generate-ssh-keys +az aks create –resource-group MyResourceGroup –name MyAKS –location eastus –node-count 1 –generate-ssh-keys -az aks create –resource-group yResourceGroup –name MyAKS –location eastus –node-count 1 –generate-ssh-keys +az aks create –resource-group MyResourceGroup –name MyAKS –location eastus –node-count 1 –generate-ssh-keys -az aks create –resource-group yResourceGroup –name MyAKS –location eastus –node-count 1 –generate-ssh-keys +az aks create –resource-group MyResourceGroup –name MyAKS –location eastus –node-count 1 –generate-ssh-keys

This update includes a correction to the references for Azure RBAC for Kubernetes authorization, ensuring users have accurate information for managing access.

The documentation now emphasizes the importance of IP address planning for load balancers in AKS on Azure Local, ensuring users understand the networking requirements and potential conflicts.

The documentation for AKS on Azure Local has been updated to correct links related to prerequisites, specifically changing references from "aks-hci-network-system-requirements.md" to "network-system-requirements.md." This change ensures users are directed to the correct resource for reviewing network system requirements when deploying AKS on Azure Local.

This quickstart guide has been updated to reflect changes in the command for creating a fleet with private cluster and VNet integration options. The date has also been updated to reflect the latest changes.

Learn how to enable full caching for ephemeral OS disks in Azure Kubernetes Service (AKS) to improve resiliency and performance.

The documentation now includes updated links for networking requirements related to Kubernetes, specifically directing users to the correct resources for IP address planning and networking in AKS on Azure Local. This change ensures that users have access to the most relevant and accurate information regarding IP address management to avoid conflicts in their deployments.

The documentation has been updated to correct links related to known issues in AKS enabled by Azure Arc, specifically changing references from "aks-known-issues.md" to "aks-arc-known-issues.md." This change ensures users are directed to the correct resource for troubleshooting issues related to Kubernetes cluster creation or node pool scaling failures due to AKS Arc image problems.

The documentation for AKS Arc has been updated to correct links to the network system requirements, ensuring users are directed to the correct resource. Additionally, the content clarifies that network settings can only be customized using AKS Arc defined logical networks, and not at the NIC level of node pools, which is crucial for understanding egress requirements and connectivity.