Merge pull request #270001 from schaffererin/planned-maintenance-auto-upgrade-aks-2

Added portal experience for Automatically upgrade an AKS cluster

Author: JamesJBarnett

articles/aks/auto-upgrade-cluster.md

@@ -34,7 +34,7 @@ If you’re using cluster auto-upgrade, you can no longer upgrade the control pl
 
 If using the `node-image` cluster auto-upgrade channel or the `NodeImage` node image auto-upgrade channel, Linux [unattended upgrades][unattended-upgrades] are disabled by default.
 
-## Use cluster auto-upgrade
+## Cluster auto-upgrade channels
 
 Automatically completed upgrades are functionally the same as manual upgrades. The [selected auto-upgrade channel][planned-maintenance] determines the timing of upgrades. When making changes to auto-upgrade, allow 24 hours for the changes to take effect. Automatically upgrading a cluster follows the same process as manually upgrading a cluster. For more information, see [Upgrade an AKS cluster][upgrade-aks-cluster].
 
@@ -62,38 +62,61 @@ The following upgrade channels are available:
 >
 > * Each cluster can only be associated with a single auto-upgrade channel. This is because your specified channel determines the Kubernetes version that runs on the cluster.
 
-### Use cluster auto-upgrade with a new AKS cluster
+## Use cluster auto-upgrade with a new AKS cluster
+
+### [Azure CLI](#tab/azure-cli)
 
 * Set the auto-upgrade channel when creating a new cluster using the [`az aks create`][az-aks-create] command and the `auto-upgrade-channel` parameter.
 
     ```azurecli-interactive
     az aks create --resource-group myResourceGroup --name myAKSCluster --auto-upgrade-channel stable --generate-ssh-keys
     ```
 
-### Use cluster auto-upgrade with an existing AKS cluster
+### [Azure portal](#tab/azure-portal)
+
+1. In the Azure portal, select **Create a resource** > **Containers** > **Azure Kubernetes Service (AKS)**.
+2. In the **Basics** tab, under **Cluster details**, select the desired auto-upgrade channel from the **Automatic upgrade** dropdown. We recommend selecting the **Enabled with patch (recommended)** option.
+
+    :::image type="content" source="./media/auto-upgrade-cluster/portal-autoupgrade-new-cluster.png" alt-text="The screenshot of the create blade for an AKS cluster in the Azure portal. The automatic upgrade field shows 'Enabled with patch (recommended)' selected.":::
+
+3. Complete the remaining steps to create the cluster.
+
+---
+
+## Use cluster auto-upgrade with an existing AKS cluster
+
+### [Azure CLI](#tab/azure-cli)
 
 * Set the auto-upgrade channel on an existing cluster using the [`az aks update`][az-aks-update] command with the `auto-upgrade-channel` parameter.
 
     ```azurecli-interactive
     az aks update --resource-group myResourceGroup --name myAKSCluster --auto-upgrade-channel stable
     ```
 
-## Auto-upgrade in the Azure portal
+### [Azure portal](#tab/azure-portal)
+
+1. In the Azure portal, navigate to your AKS cluster.
+2. In the **Settings** section, select **Cluster configuration**.
+3. Under **Upgrade** > **Kubernetes version**, select **Upgrade version**.
 
-If using the Azure portal, you can find auto-upgrade settings under the **Settings** > **Cluster configuration** blade by selecting **Upgrade version**. The `Patch` channel is selected by default.
+    :::image type="content" source="./media/auto-upgrade-cluster/portal-autoupgrade-existing-cluster.png" alt-text="The screenshot of the upgrade blade for an AKS cluster in the Azure portal.":::
 
-:::image type="content" source="./media/auto-upgrade-cluster/portal-upgrade.png" alt-text="The screenshot of the upgrade blade for an AKS cluster in the Azure portal. The automatic upgrade field shows 'patch' selected, and several APIs deprecated between the selected Kubernetes version and the cluster's current version are described.":::
+4. On the **Upgrade Kubernetes version** page, select the desired auto-upgrade channel from the **Automatic upgrade** dropdown. We recommend selecting the **Enabled with patch (recommended)** option.
 
-The Azure portal also highlights all the deprecated APIs between your current version and newer, available versions you intend to migrate to. For more information, see the [Kubernetes API removal and deprecation process][k8s-deprecation].
+    :::image type="content" source="./media/auto-upgrade-cluster/portal-autoupgrade-upgrade-page-existing-cluster.png" alt-text="The screenshot of the Upgrade Kubernetes page for an AKS cluster in the Azure portal.":::
+
+5. Select **Save**.
+
+---
 
 ## Use auto-upgrade with Planned Maintenance
 
-If using  Planned Maintenance and cluster auto-upgrade, your upgrade starts during your specified maintenance window.
+If using Planned Maintenance and cluster auto-upgrade, your upgrade starts during your specified maintenance window.
 
 > [!NOTE]
 > To ensure proper functionality, use a maintenance window of *four hours or more*.
 
-For more information on Planned Maintenance, see [Use Planned Maintenance to schedule maintenance windows for your Azure Kubernetes Service (AKS) cluster][planned-maintenance].
+For more information on how to set a maintenance window with Planned Maintenance, see [Use Planned Maintenance to schedule maintenance windows for your Azure Kubernetes Service (AKS) cluster][planned-maintenance].
 
 ## Best practices for cluster auto-upgrade
 

articles/aks/media/auto-upgrade-cluster/portal-autoupgrade-existing-cluster.png

@@ -74,7 +74,7 @@ Note the following important changes before you upgrade to any of the available
 > [!NOTE]
 > Alias minor version requires Azure CLI version 2.37 or above as well as API version 20220401 or above. Use `az upgrade` to install the latest version of the CLI.
 
-AKS allows you to create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster runs the minor version's latest GA patch. For example, if you create a cluster with **`1.21`**, your cluster runs **`1.21.7`**, which is the latest GA patch version of *1.21*. If you want to upgrade your patch version in the same minor version, please use [auto-upgrade](./auto-upgrade-cluster.md#use-cluster-auto-upgrade).
+AKS allows you to create a cluster without specifying the exact patch version. When you create a cluster without designating a patch, the cluster runs the minor version's latest GA patch. For example, if you create a cluster with **`1.21`**, your cluster runs **`1.21.7`**, which is the latest GA patch version of *1.21*. If you want to upgrade your patch version in the same minor version, please use [auto-upgrade](./auto-upgrade-cluster.md).
 
 To see what patch you're on, run the `az aks show --resource-group myResourceGroup --name myAKSCluster` command. The `currentKubernetesVersion` property shows the whole Kubernetes version.
 

articles/aks/media/auto-upgrade-cluster/portal-autoupgrade-new-cluster.png

@@ -1,6 +1,6 @@
 ---
 title: Azure Linux Container Host for AKS tutorial - Upgrade Azure Linux Container Host nodes
-description: In this Azure Linux Container Host for AKS tutorial, you will learn how to upgrade Azure Linux Container Host nodes.
+description: In this Azure Linux Container Host for AKS tutorial, you learn how to upgrade Azure Linux Container Host nodes.
 author: htaubenfeld
 ms.author: htaubenfeld
 ms.service: microsoft-linux
@@ -12,22 +12,23 @@ ms.date: 05/10/2023
 
 The Azure Linux Container Host ships updates through two mechanisms: updated Azure Linux node images and automatic package updates.
 
-As part of the application and cluster lifecycle, we recommend keeping your clusters up to date and secured by enabling upgrades for your cluster. To automatically keep your clusters up to date and secured, you can enable automatic node-image upgrades so your cluster will use the latest Azure Linux Container Host image when it scales up. Upgrading clusters can also be done manually.
+As part of the application and cluster lifecycle, we recommend keeping your clusters up to date and secured by enabling upgrades for your cluster. You can enable automatic node-image upgrades to ensure your clusters use the latest Azure Linux Container Host image when it scales up. You can also manually upgrade the node-image on a cluster.
 
-In this tutorial, part five of five, you will learn how to:
+In this tutorial, part five of five, you learn how to:
 
 > [!div class="checklist"]
+>
 > * Manually upgrade the node-image on a cluster.
 > * Automatically upgrade an Azure Linux Container Host cluster.
 > * Deploy Kured in an Azure Linux Container Host cluster.
 
 > [!NOTE]
-> Any upgrade operation, whether performed manually or automatically, will upgrade the node image version if not already on the latest. The latest version is contingent on a full AKS release, and can be determined by visiting the [AKS release tracker](../../articles/aks/release-tracker.md).
+> Any upgrade operation, whether performed manually or automatically, upgrades the node image version if not already on the latest. The latest version is contingent on a full AKS release, and can be determined by visiting the [AKS release tracker](../../articles/aks/release-tracker.md).
 
 ## Prerequisites
 
-- In previous tutorials, you created and deployed an Azure Linux Container Host cluster. To complete this tutorial, you need an existing cluster. If you haven't done this step and would like to follow along, start with [Tutorial 1: Create a cluster with the Azure Linux Container Host for AKS](./tutorial-azure-linux-create-cluster.md).
-- You need the latest version of Azure CLI. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
+* In previous tutorials, you created and deployed an Azure Linux Container Host cluster. To complete this tutorial, you need an existing cluster. If you haven't done this step and would like to follow along, start with [Tutorial 1: Create a cluster with the Azure Linux Container Host for AKS](./tutorial-azure-linux-create-cluster.md).
+* You need the latest version of Azure CLI. Find the version using the `az --version` command. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).
 
 ## Manually upgrade your cluster
 
@@ -45,22 +46,21 @@ az aks nodepool upgrade \
 
 Auto-upgrade provides a set once and forget mechanism that yields tangible time and operational cost benefits. By enabling auto-upgrade, you can ensure your clusters are up to date and don't miss the latest Azure Linux Container Host features or patches from AKS and upstream Kubernetes.
 
-Automatically completed upgrades are functionally the same as manual upgrades. The timing of upgrades is determined by the selected channel. When making changes to auto-upgrade, allow 24 hours for the changes to take effect.
+Automatically completed upgrades are functionally the same as manual upgrades. The selected channel determines the timing of upgrades. When making changes to auto-upgrade, allow 24 hours for the changes to take effect.
 
-To set the auto-upgrade channel on existing cluster, update the `--auto-upgrade-channel` parameter, similar to the following example which automatically upgrades the cluster to the latest supported patch release of a previous minor version.
+To set the auto-upgrade channel on existing cluster, update the `--auto-upgrade-channel` parameter, similar to the following example, which automatically upgrades the cluster to the latest supported patch release of a previous minor version.
 
 ```azurecli-interactive
 az aks update --resource-group testAzureLinuxResourceGroup --name testAzureLinuxCluster --auto-upgrade-channel stable
 ```
 
-For more information on upgrade channels, see [Using cluster auto-upgrade](../../articles/aks/auto-upgrade-cluster.md#use-cluster-auto-upgrade).
+For more information on upgrade channels, see [Using cluster auto-upgrade](../../articles/aks/auto-upgrade-cluster.md).
 
 ## Enable automatic package upgrades
 
 Similar to setting your clusters to auto-upgrade, you can use the same set once and forget mechanism for package upgrades by enabling the node-os upgrade channel. If automatic package upgrades are enabled, the dnf-automatic systemd service runs daily and installs any updated packages that have been published.
 
-To set the node-os upgrade channel on existing cluster, update the `--node-os-upgrade-channel` parameter, similar to the following example which automatically enables package upgrades. Note, that for some settings of [Node OS Upgrade Channel](../../articles/aks/auto-upgrade-node-image.md), `dnf-automatic` will be disabled by default.
-
+To set the node-os upgrade channel on existing cluster, update the `--node-os-upgrade-channel` parameter, similar to the following example, which automatically enables package upgrades. Note that for some settings of [Node OS Upgrade Channel](../../articles/aks/auto-upgrade-node-image.md), `dnf-automatic` is disabled by default.
 
 ```azurecli-interactive
 az aks update --resource-group testAzureLinuxResourceGroup --name testAzureLinuxCluster --node-os-upgrade-channel Unmanaged
@@ -70,7 +70,7 @@ az aks update --resource-group testAzureLinuxResourceGroup --name testAzureLinux
 
 To protect your clusters, security updates are automatically applied to Azure Linux nodes. These updates include OS security fixes, kernel updates, and package upgrades. Some of these updates require a node reboot to complete the process. AKS doesn't automatically reboot these nodes to complete the update process.
 
-We recommend enabling an automatic reboot daemon such as [Kured](https://kured.dev/docs/) so that your cluster can reboot nodes that have taken kernel updates. To deploy the Kured DaemonSet in an Azure Linux Container Host cluster, see [Deploy kured in an AKS cluster](../../articles/aks/node-updates-kured.md#deploy-kured-in-an-aks-cluster)
+We recommend enabling an automatic reboot daemon, such as [Kured](https://kured.dev/docs/), so that your cluster can reboot nodes that have taken kernel updates. To deploy the Kured DaemonSet in an Azure Linux Container Host cluster, see [Deploy Kured in an AKS cluster](../../articles/aks/node-updates-kured.md#deploy-kured-in-an-aks-cluster).
 
 ## Clean up resources
 
@@ -85,6 +85,7 @@ az group delete --name testAzureLinuxCluster --yes --no-wait
 In this tutorial, you upgraded your Azure Linux Container Host cluster. You learned how to: 
 
 > [!div class="checklist"]
+>
 > * Manually upgrade the node-image on a cluster.
 > * Automatically upgrade an Azure Linux Container Host cluster.
 > * Deploy kured in an Azure Linux Container Host cluster.