public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-04-25 07:45:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add prerequisite for AKS import

Browse Source
This commit is contained in:
yiannistri
2024-12-11 14:39:57 +00:00
parent ca818e70af
commit 6b44b6f9c5
3 changed files with 48 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
View File

@@ -35,6 +35,8 @@ Since, by default, Google Kubernetes Engine (GKE) doesn't grant the `cluster-adm
To successfully import or provision EKS, AKS, and GKE clusters from Rancher, the cluster must have at least one managed node group.
AKS clusters can be imported only if local accounts are enabled. If a cluster is configured to use Microsoft Entra ID for authentication, then Rancher will not be able to import it and report an error.
EKS Anywhere clusters can be imported/registered into Rancher with an API address and credentials, as with any downstream cluster. EKS Anywhere clusters are treated as imported clusters and do not have full lifecycle support from Rancher.
GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard](https://cloud.google.com/kubernetes-engine/docs/resources/autopilot-standard-feature-comparison) for more information about the differences between GKE modes.
@@ -286,3 +288,17 @@ To annotate a registered cluster,
6. Click **Save**.
**Result:** The annotation does not give the capabilities to the cluster, but it does indicate to Rancher that the cluster has those capabilities.
## Troubleshooting
This section lists some of the most common errors that may occur when importing a cluster, along with steps to troubleshoot them.
### AKS
#### Error: Getting static credential is not allowed because this cluster is set to disable local accounts.
* This may occur if your cluster has disabled local accounts. Enable local accounts before attempting to import the cluster again:
```
az aks update --resource-group <resource-group> --name <cluster-name> --enable-local-accounts
```

16
versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
View File

@@ -35,6 +35,8 @@ Since, by default, Google Kubernetes Engine (GKE) doesn't grant the `cluster-adm
To successfully import or provision EKS, AKS, and GKE clusters from Rancher, the cluster must have at least one managed node group.
AKS clusters can be imported only if local accounts are enabled. If a cluster is configured to use Microsoft Entra ID for authentication, then Rancher will not be able to import it and report an error.
EKS Anywhere clusters can be imported/registered into Rancher with an API address and credentials, as with any downstream cluster. EKS Anywhere clusters are treated as imported clusters and do not have full lifecycle support from Rancher.
GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard](https://cloud.google.com/kubernetes-engine/docs/resources/autopilot-standard-feature-comparison) for more information about the differences between GKE modes.
@@ -286,3 +288,17 @@ To annotate a registered cluster,
6. Click **Save**.
**Result:** The annotation does not give the capabilities to the cluster, but it does indicate to Rancher that the cluster has those capabilities.
## Troubleshooting
This section lists some of the most common errors that may occur when importing a cluster, along with steps to troubleshoot them.
### AKS
#### Error: Getting static credential is not allowed because this cluster is set to disable local accounts.
* This may occur if your cluster has disabled local accounts. Enable local accounts before attempting to import the cluster again:
```
az aks update --resource-group <resource-group> --name <cluster-name> --enable-local-accounts
```

16
versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
View File

@@ -35,6 +35,8 @@ Since, by default, Google Kubernetes Engine (GKE) doesn't grant the `cluster-adm
To successfully import or provision EKS, AKS, and GKE clusters from Rancher, the cluster must have at least one managed node group.
AKS clusters can be imported only if local accounts are enabled. If a cluster is configured to use Microsoft Entra ID for authentication, then Rancher will not be able to import it and report an error.
EKS Anywhere clusters can be imported/registered into Rancher with an API address and credentials, as with any downstream cluster. EKS Anywhere clusters are treated as imported clusters and do not have full lifecycle support from Rancher.
GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard](https://cloud.google.com/kubernetes-engine/docs/resources/autopilot-standard-feature-comparison) for more information about the differences between GKE modes.
@@ -286,3 +288,17 @@ To annotate a registered cluster,
6. Click **Save**.
**Result:** The annotation does not give the capabilities to the cluster, but it does indicate to Rancher that the cluster has those capabilities.
## Troubleshooting
This section lists some of the most common errors that may occur when importing a cluster, along with steps to troubleshoot them.
### AKS
#### Error: Getting static credential is not allowed because this cluster is set to disable local accounts.
* This may occur if your cluster has disabled local accounts. Enable local accounts before attempting to import the cluster again:
```
az aks update --resource-group <resource-group> --name <cluster-name> --enable-local-accounts
```