Merge pull request #259955 from schaffererin/temp-removal-aks-ai-toolchain-operator-doc

Temporary removal of AKS AI toolchain operator doc while technical issues are being resolved

Author: v-dirichards

articles/aks/TOC.yml

@@ -755,8 +755,6 @@
           href: open-ai-quickstart.md
         - name: Secure access to Azure OpenAI from Azure Kubernetes Service (AKS)
           href: open-ai-secure-access-quickstart.md
-        - name: Deploy an AI model with the AI toolchain operator
-          href: ai-toolchain-operator.md 
     - name: DevOps
       items:
         - name: Azure DevOps Project

articles/aks/supported-kubernetes-versions.md

@@ -76,11 +76,9 @@ Note the following important changes to make before you upgrade to any of the av
 > [!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*.
+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).
 
-When you upgrade by alias minor version, only a higher minor version is supported. For example, upgrading from `1.14.x` to `1.14` doesn't trigger an upgrade to the latest GA `1.14` patch, but upgrading to `1.15` triggers an upgrade to the latest GA `1.15` patch.
-
-To see what patch you're on, run the `az aks show --resource-group myResourceGroup --name myAKSCluster` command. The property `currentKubernetesVersion` shows the whole Kubernetes version.
+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.
 
 ```
 {
@@ -115,7 +113,7 @@ New minor version    |    Supported Version List
 -----------------    |    ----------------------
 1.17.a               |    1.17.a, 1.17.b, 1.16.c, 1.16.d, 1.15.e, 1.15.f
 
-When a new minor version is introduced, the oldest supported minor version and patch releases are deprecated and removed. For example, the current supported version list is:
+When a new minor version is introduced, the oldest minor version and patch releases supported are deprecated and removed. For example, let's say the current supported version list is:
 
 ```
 1.17.a
@@ -128,7 +126,6 @@ When a new minor version is introduced, the oldest supported minor version and p
 
 When AKS releases 1.18.\*, all the 1.15.\* versions go out of support 30 days later.
 
-
 AKS also supports a maximum of two **patch** releases of a given minor version. For example, given the following supported versions:
 
 ```
@@ -285,13 +282,17 @@ Downgrades aren't supported.
 
 Additionally, AKS doesn't make any runtime or other guarantees for clusters outside of the supported versions list.
 
-### What happens when a user scales a Kubernetes cluster with a minor version that isn't supported?
+### What happens when you scale a Kubernetes cluster with a minor version that isn't supported?
 
 For minor versions not supported by AKS, scaling in or out should continue to work. Since there are no guarantees with quality of service, we recommend upgrading to bring your cluster back into support.
 
-### Can a user stay on a Kubernetes version forever?
+### Can you stay on a Kubernetes version forever?
+
+If a cluster has been out of support for more than three (3) minor versions and has been found to carry security risks, Azure proactively contacts you to  upgrade your cluster. If you don't take further action, Azure reserves the right to automatically upgrade your cluster on your behalf.
 
-If a cluster has been out of support for more than three (3) minor versions and has been found to carry security risks, Azure proactively contacts you to upgrade your cluster. If you don't take further action, Azure reserves the right to automatically upgrade your cluster on your behalf.
+### What happens if you scale a Kubernetes cluster with a minor version that isn't supported?
+
+For minor versions not supported by AKS, scaling in or out should continue to work. Since there are no guarantees with quality of service, we recommend upgrading to bring your cluster back into support.
 
 ### What version does the control plane support if the node pool isn't in one of the supported AKS versions?