The documentation now specifies that when creating Windows node pools, users should use `–os-sku Windows2025` along with `–enable-fips-image`, as Windows Server 2025 requires a FIPS-enabled image. Additionally, the default Kubernetes versions for Windows OS types have been updated, with Windows2025 now being the default for Kubernetes version 1.36 and later.

Guidance on rollback strategies for Kubernetes migration on Azure Kubernetes Service (AKS)

The document has been updated to clarify upgrade paths for Kubernetes versions in Azure AKS. It includes new examples and explanations regarding supported and unsupported versions, as well as the implications of skipping minor versions during upgrades. Additionally, it emphasizes the importance of following version skew policies when upgrading control planes and node pools.

The documentation has been updated to clarify the behavior of private AKS clusters regarding public DNS names. It specifies that using the `–disable-public-fqdn` option removes the public DNS name and restricts cluster management access to private connectivity methods. This change enhances the understanding of how to manage access to private clusters effectively.

This document has been updated to include new information about filtering gates by type in Azure CLI commands, specifically for approval gates. The date has also been updated to reflect the latest changes.

The documentation now specifies that Windows Server 2025 is the default operating system for Kubernetes version 1.36 and later, while Windows Server 2022 remains the default for versions 1.25-1.35. Users must include the `–enable-fips-image` parameter when creating Windows Server 2025 node pools using the `az aks nodepool add` command, as FIPS-enabled images are required. Additionally, Windows Server 2019 has been removed as an option in the quickstart guides, reflecting its retirement timeline.

This new document provides a comprehensive guide on using scheduled start gates in Azure Kubernetes Fleet Manager update run strategies. It explains how to schedule updates for clusters, including prerequisites, configuration steps, and examples of JSON files for defining stages and groups with scheduled start gates.

The document has been updated to reflect changes in certificate rotation procedures, specifically the auto-rotation feature. The updates include a refresh of the documentation to clarify the process and provide better guidance for users managing certificate rotation in Azure Kubernetes Service (AKS).

Updated the AKSNodeClass documentation to clarify the options available for node provisioning, including the removal of outdated references. This change ensures users have accurate and relevant information for configuring node classes.

The document has been updated to fix formatting issues in the AKS managed GPU node class YAML example, ensuring clarity and correctness in the configuration details for users implementing GPU nodes in Azure Kubernetes Service.

The documentation for creating Azure file shares has been updated to include new parameters such as `enableLargeFileShares`, which allows users to specify if large file shares should be enabled for Standard accounts, and `provisionedBandwidth` and `provisionedIOPS`, which define throughput and IOPS for the Azure Files provisioned v2 model. Additionally, the `folderName` parameter now supports placeholders for dynamic naming, and the `useDataPlaneAPI` parameter has been enhanced to include an `oauth` option for authentication. Users can also now control shared key access and encryption in transit for NFS shares.

The documentation now includes a new section on "Migration cutover rollback," which provides users with a strategy for instant rollback to the source environment during workload migrations to AKS. Users can implement a blue-green dual-cluster approach or use node pools within the new AKS cluster, allowing for a seamless cutover and immediate traffic reversal if issues arise. Additionally, detailed implementation steps and rollback triggers have been added to enhance user guidance during the migration process.

The documentation now specifies that Windows Server 2022 is the default OS for Kubernetes versions 1.25 to 1.35, while Windows Server 2025 is the default OS for Kubernetes version 1.36 and later. This change clarifies the host OS version compatibility for users deploying AKS with different Kubernetes versions, ensuring they are aware of the correct default OS to use.

The update includes clarifications on generating update runs from auto-upgrade profiles, emphasizing that existing update runs may not be modified if they share the same upgrade specification. This change improves the documentation’s accuracy and helps users understand the behavior of update runs in AKS.

This update adds troubleshooting steps for the Inspektor Gadget extension in Azure Kubernetes Service (AKS), specifically addressing installation failures related to the PodMonitor custom resource. It includes symptoms, causes, and resolutions for common issues, enhancing the documentation’s usability for users facing these problems.

The documentation now includes detailed instructions for migrating from the cluster autoscaler to node auto-provisioning (NAP), outlining two distinct paths: disabling the cluster autoscaler first or allowing both to coexist. Users can register the `AllowClusterAutoscalerAndNAP` feature flag to enable both systems in the same cluster, but they must implement taints and tolerations to prevent double provisioning of nodes. Additionally, users are guided on how to manage workloads during the migration process, including adding specific tolerations to workloads and taints to node pools to control scheduling behavior.

A new document has been added to guide users on troubleshooting issues related to Kubernetes version image readiness in AKS on Azure Local. It outlines symptoms, causes, and steps to resolve common problems, providing valuable support for administrators managing AKS Arc clusters.

Revised the TLS certificate supply options for Azure Key Vault, providing clearer instructions on how to manage certificates and keys. This change enhances the usability of the documentation for users implementing TLS in AKS.

This guide provides a four-phase framework for assessing and migrating legacy applications to Azure Kubernetes Service (AKS), including practical migration pathways, Windows and .NET Framework specifics, operational checks, and a FAQ. It emphasizes the importance of a disciplined assessment before migration.

The documentation now includes a clarification regarding the compatibility of the Node Auto Provisioning (NAP) feature with clusters that have the cluster autoscaler enabled. Users will be informed that enabling NAP on such clusters is not possible, ensuring they understand the limitations when configuring their AKS environments.

The documentation for customer-managed keys has been enhanced to include RBAC role assignments for Key Vaults and clarify that the Disk Encryption Set (DES) only requires Reader role access, not Contributor. Additionally, the commands for setting up access have been updated for clarity.

The documentation now includes a new section on checking directory and subscription settings, guiding users to navigate to the Azure portal and ensure their default subscription filter includes the relevant subscription for deployment. Additionally, users are provided with commands to register the hidden preview feature using the Azure CLI, enhancing their ability to manage subscriptions effectively.

This article provides a comprehensive guide on how to move a Kubernetes workload from one cluster to another using Azure Kubernetes Fleet Manager resource placement. It includes prerequisites, sample workloads, and detailed steps for managing workloads across clusters, enhancing operational efficiency.

The documentation now clarifies that Windows Server 2025 is the default operating system for Kubernetes version 1.36 and later, and users must include the `-EnableFIPS` parameter when creating Windows Server 2025 node pools. Additionally, Windows Server 2019 has been removed as an option in the quickstart, and the ASP.NET sample application now requires Windows Server containers to be based on images of Windows Server 2022 or greater. Users should also note that Windows Server 2022 will retire in June 2028.

This document has been updated to reflect changes in image references for the kuard demo application, ensuring users have the correct and up-to-date information for DNS load balancing in Kubernetes environments.

Updated the address range restrictions for AKS clusters, clarifying that they cannot use specific CIDR ranges for Kubernetes services, pods, or cluster virtual networks. This change enhances the documentation’s accuracy regarding network configurations.

The documentation now clarifies that when creating a Windows Server 2025 node pool using the `az aks nodepool add` command, users must include the `–enable-fips-image` parameter to ensure the use of a FIPS-enabled image. This change is crucial for users deploying Windows Server 2025 node pools, as it specifies a requirement that was previously not highlighted.

The documentation for AKS node images has been updated to include new variants of the ACL node image that support Federal Information Processing Standards (FIPS) and Trusted Launch for both AMD64 and ARM64 architectures. This change improves clarity on compliance and security options available for users.

The service mesh integration documentation has been updated to reflect the new version 1.11.3. This includes important changes that enhance the integration capabilities of the service mesh with AKS, ensuring users have the latest information.

The documentation now specifies that Windows Server 2025 node pools require a FIPS-enabled image, and users must include `–enable-fips-image` in Azure CLI or `-EnableFIPS` in Azure PowerShell when adding these node pools. Additionally, the sample output for Windows Server 2025 node pools has been updated to reflect the correct version and configuration details.

The documentation for Artifact Streaming on Azure Kubernetes Service (AKS) has been updated to clarify that users can now enable and disable the Artifact Streaming feature on their AKS node pools, which helps reduce deployment times. Additionally, the article emphasizes that Artifact Streaming is only supported on Premium SKU Azure Container Registries and provides specific commands for creating and updating node pools with this feature enabled. Users are also informed about the limitations regarding supported architectures and the requirement for Kubernetes version 1.25 or later.

The release notes for the ALB Controller have been updated to reflect version 1.11.3, which includes security patches, WAF fixes, and Istio service mesh integration improvements. This update is crucial for users to stay informed about the latest enhancements and fixes.

The updated article provides an overview of certificate management and rotation in Azure Kubernetes Service (AKS), including how to manually rotate certificates and enable autorotation for enhanced security. It emphasizes the importance of certificate expiration management.

The tutorial on preparing a multi-container application for Kubernetes has been updated to include new tools and methods for converting Docker Compose files to Kubernetes manifests. Users can now utilize tools like Kompose, Move2Kube, Docker Compose Bridge, and Podman for this conversion, along with AI-assisted options for drafting manifests. Additionally, the tutorial emphasizes the importance of reviewing and adjusting generated manifests for Azure Kubernetes Service (AKS) deployment, including updates to image references and handling of storage and secrets.

Learn how to configure and manage Node Disruption Policy to control when operations that require node reimage are allowed in Azure Kubernetes Service (AKS).

This article explains how to manage and rotate certificates in Azure Kubernetes Service (AKS) clusters to maintain secure communication between components and ensure compliance. It includes prerequisites, commands for checking certificate expiration dates, and instructions for managing certificates effectively.

This article describes practical, production-focused approaches for migrating existing workloads to Azure Kubernetes Service (AKS) with minimal or zero downtime. It includes a quick runbook for provisioning AKS, deploying applications, syncing data, and shifting traffic progressively, along with a comparison of migration strategies.

This newly added article introduces Artifact Streaming on AKS, explaining how it works with Azure Container Registry (ACR) to optimize container image pulls. It highlights the benefits of reduced deployment times and improved efficiency, making it a significant addition for users managing containerized applications.

The quickstart guide for deploying the application gateway for containers has been updated to version 1.11.3. This includes changes in the versioning details, which are essential for users to follow the latest deployment practices.

The documentation now specifies that users should select **Windows Server 2025** for node pools, which requires enabling a FIPS-enabled image. Additionally, the output examples for the `kubectl get nodes -o wide` command have been updated to reflect the new node pool configurations, including details such as internal and external IP addresses, OS image, and container runtime for Windows Server 2025. Windows Server 2019 has been removed as an option from the quickstart guide.

Revised the limitations section for the Vertical Pod Autoscaler (VPA), emphasizing that VPA guarantees optimal support for up to 1,000 pods per cluster. This update provides clearer guidance on scalability and resource management.

The documentation now includes a new section on "Scheduled start gates," which allows users to pause the update run until a specified day and time, providing more control over deployment timing. Additionally, the existing "Approval gates" section has been clarified to emphasize that approvals can be configured before or after each stage or group, enhancing the understanding of how to manage update approvals effectively. The mention of disabling Linux unmanaged upgrades has been removed, indicating a shift in how users may manage their upgrade settings.

Updates have been made to clarify the performance management of Azure Premium SSD v2 disks in AKS. Users are informed that post-provisioning changes to IOPS and throughput cannot be configured through AKS node pool settings and must be done via the Kubernetes CSI driver or directly on the managed disk using Azure CLI.

The document outlines the retirement of the `aks-disable-kubelet-serving-certificate-rotation=true` node pool tag, effective from April 1, 2027. It explains the implications for existing node pools and provides guidance on updating workloads accordingly.

This document introduces the Node Disruption Policy in Azure Kubernetes Service (AKS), detailing how to control when operations that require node reimage are allowed. It provides insights into policy configurations, prerequisites, and the impact of these policies on workload stability.