Skip to content

Commit

Permalink
Merge pull request #155 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history 
8/27/2024 PM Publish
  • Loading branch information
@Taojunshen
Taojunshen authored Aug 27, 2024
2 parents c058b10 + 0902378 commit a84d369
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions articles/aks/auto-upgrade-cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ AKS follows a strict supportability versioning window. With properly selected au

You can specify cluster auto-upgrade specifics using the following guidance. The upgrades occur based on your specified cadence and are recommended to remain on supported Kubernetes versions.

AKS also initiates auto-upgrades for unsupported clusters. When a cluster in an n-3 version (where n is the latest supported AKS GA minor version) is about to drop to n-4, AKS automatically upgrades the cluster to n-2 to remain in an AKS support [policy][supported-kubernetes-versions]. Automatically upgrading a platform supported cluster to a supported version is enabled by default. Stopped node pools will be upgraded during an auto-upgrade operation. The upgrade will apply to nodes when the node pool is started. To minimize disruptions, set up [maintenance windows][planned-maintenance].
AKS also initiates auto-upgrades for unsupported clusters. When a cluster in an n-3 version (where n is the latest supported AKS GA minor version) is about to drop to n-4, AKS automatically upgrades the cluster to n-2 to remain in an AKS support [policy][supported-kubernetes-versions]. Automatically upgrading a platform supported cluster to a supported version is enabled by default. Stopped node pools are upgraded during an auto-upgrade operation. The upgrade applies to nodes when the node pool is started. To minimize disruptions, set up [maintenance windows][planned-maintenance].

## Cluster auto-upgrade limitations

Expand All @@ -47,7 +47,7 @@ The following upgrade channels are available:
| `patch`| automatically upgrades the cluster to the latest supported patch version when it becomes available while keeping the minor version the same.| For example, if a cluster runs version *1.17.7*, and versions *1.17.9*, *1.18.4*, *1.18.6*, and *1.19.1* are available, the cluster upgrades to *1.17.9*.|
| `stable`| automatically upgrades the cluster to the latest supported patch release on minor version *N-1*, where *N* is the latest supported minor version.| For example, if a cluster runs version *1.17.7* and versions *1.17.9*, *1.18.4*, *1.18.6*, and *1.19.1* are available, the cluster upgrades to *1.18.6*.|
| `rapid`| automatically upgrades the cluster to the latest supported patch release on the latest supported minor version.| In cases where the cluster's Kubernetes version is an *N-2* minor version, where *N* is the latest supported minor version, the cluster first upgrades to the latest supported patch version on *N-1* minor version. For example, if a cluster runs version *1.17.7* and versions *1.17.9*, *1.18.4*, *1.18.6*, and *1.19.1* are available, the cluster first upgrades to *1.18.6*, then upgrades to *1.19.1*.|
| `node-image`(legacy)| automatically upgrades the node image to the latest version available.| Microsoft provides patches and new images for image nodes frequently (usually weekly), but your running nodes don't get the new images unless you do a node image upgrade. Turning on the node-image channel automatically updates your node images whenever a new version is available. If you use this channel, Linux [unattended upgrades] are disabled by default. Node image upgrades work on patch versions that are deprecated, so long as the minor Kubernetes version is still supported. This channel is no longer recommended and is set to be deprecated in future. For an option that can automatically upgrade node images, see the `NodeImage` channel in [node image auto-upgrade][node-image-auto-upgrade]. |
| `node-image`(legacy)| automatically upgrades the node image to the latest version available.| Microsoft provides patches and new images for image nodes frequently (usually weekly), but your running nodes don't get the new images unless you do a node image upgrade. Turning on the node-image channel automatically updates your node images whenever a new version is available. If you use this channel, Linux [unattended upgrades] are disabled by default. Node image upgrades work on patch versions that are deprecated, so long as the minor Kubernetes version is still supported. This channel is no longer recommended and is planned for deprecation in future. For an option that can automatically upgrade node images, see the `NodeImage` channel in [node image auto-upgrade][node-image-auto-upgrade]. |

> [!NOTE]
>
Expand Down Expand Up @@ -97,7 +97,7 @@ The following upgrade channels are available:
### [Azure portal](#tab/azure-portal)

1. In the Azure portal, navigate to your AKS cluster.
2. In the **Settings** section, select **Cluster configuration**.
2. In the service menu, under **Settings**, select **Cluster configuration**.
3. Under **Upgrade** > **Kubernetes version**, select **Upgrade version**.

:::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.":::
Expand Down
Binary file modified articles/aks/media/supported-kubernetes-versions/kubernetes-versions-gantt.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 3 additions & 3 deletions articles/aks/tutorial-kubernetes-upgrade-cluster.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ If using Azure PowerShell, this tutorial requires Azure PowerShell version 5.9.0

1. Sign in to the [Azure portal](https://portal.azure.com).
2. Navigate to your AKS cluster.
3. Under **Settings**, select **Cluster configuration**.
3. From the service menu, under **Settings**, select **Cluster configuration**.
4. In **Kubernetes version**, select **Upgrade version**. This redirects you to a new page.
5. In **Kubernetes version**, select the version to check for available upgrades.

Expand Down Expand Up @@ -218,7 +218,7 @@ You can either [manually upgrade your cluster](#manually-upgrade-cluster) or [co
#### [Azure portal](#tab/azure-portal)

1. In the Azure portal, navigate to your AKS cluster.
2. Under **Settings**, select **Cluster configuration**.
2. From the service menu, under **Settings**, select **Cluster configuration**.
3. In **Kubernetes version**, select **Upgrade version**. This redirects you to a new page.
4. In **Kubernetes version**, select your desired version and then select **Save**.

Expand Down Expand Up @@ -249,7 +249,7 @@ It takes a few minutes to upgrade the cluster, depending on how many nodes you h
#### [Azure portal](#tab/azure-portal)

1. In the Azure portal, navigate to your AKS cluster.
2. Under **Settings**, select **Cluster configuration**.
2. From the service menu, under **Settings**, select **Cluster configuration**.
3. In **Kubernetes version**, select **Upgrade version**.
4. For **Automatic upgrade**, select **Enabled with patch (recommended)** > **Save**.

Expand Down

0 comments on commit a84d369

Please sign in to comment.