From 4a5ee01c18c378692144bdfdc743e38c6fcefdda Mon Sep 17 00:00:00 2001 From: Jen Travinski Date: Tue, 7 Sep 2021 18:24:44 -0400 Subject: [PATCH] Documented that AKS cluster might take hours to show up in Cluster To register list, based on region. (#3488) * Added note about AKS cluster under admin * Added note about AKS cluster under provisioning * Updated UI code for admin/provisioning note * Updated provisioning after clarifying region and UI command * Updated admin after clarifying region and UI command * Corrected UI tag --- .../editing-clusters/aks-config-reference/_index.md | 2 ++ .../hosted-kubernetes-clusters/aks/_index.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/content/rancher/v2.6/en/cluster-admin/editing-clusters/aks-config-reference/_index.md b/content/rancher/v2.6/en/cluster-admin/editing-clusters/aks-config-reference/_index.md index 7f5b7d14e9b..02b70c5ee55 100644 --- a/content/rancher/v2.6/en/cluster-admin/editing-clusters/aks-config-reference/_index.md +++ b/content/rancher/v2.6/en/cluster-admin/editing-clusters/aks-config-reference/_index.md @@ -169,6 +169,8 @@ The first way to ensure that Rancher is running on the same [NAT](https://docs.m The second way is to run a command to register the cluster with Rancher. Once the cluster is provisioned, you can run the displayed command anywhere you can connect to the cluster’s Kubernetes API. This command is displayed in a pop-up when you provision an AKS cluster with a private API endpoint enabled. +> **Note:** Please be aware that when registering an existing AKS cluster, the cluster might take some time, possibly hours, to appear in the `Cluster To register` dropdown list. This outcome will be based on region. + For more information about connecting to an AKS private cluster, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/private-clusters#options-for-connecting-to-the-private-cluster) # Node Pools diff --git a/content/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md b/content/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md index 618b8ec318b..64157308900 100644 --- a/content/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md +++ b/content/rancher/v2.6/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md @@ -144,6 +144,8 @@ The first way to ensure that Rancher is running on the same [NAT](https://docs.m The second way is to run a command to register the cluster with Rancher. Once the cluster is provisioned, you can run the displayed command anywhere you can connect to the cluster’s Kubernetes API. This command is displayed in a pop-up when you provision an AKS cluster with a private API endpoint enabled. +> **Note:** Please be aware that when registering an existing AKS cluster, the cluster might take some time, possibly hours, to appear in the `Cluster To register` dropdown list. This outcome will be based on region. + For more information about connecting to an AKS private cluster, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/private-clusters#options-for-connecting-to-the-private-cluster) # Syncing