public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 21:18:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1590 from yiannistri/update-aks-import-docs

Browse Source 
Add prerequisite for AKS import
This commit is contained in:
Lucas Saintarbor
2025-01-16 09:52:49 -08:00
committed by GitHub
parent 2026d15d3a e5176e033b
commit 7cc5f27bc5
6 changed files with 60 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+19
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,20 @@ 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
- The following error may occur if local accounts are disabled in your cluster.
```sh
Error: Getting static credential is not allowed because this cluster is set to disable local accounts.
```
To resolve this issue, enable local accounts before attempting to [import the cluster](#registering-a-cluster) again.
```sh
az aks update --resource-group <resource-group> --name <cluster-name> --enable-local-accounts
```
versioned_docs/version-2.10/reference-guides/cluster-configuration/rancher-server-configuration/aks-cluster-configuration.md
+1 -1
View File
@@ -8,7 +8,7 @@ title: AKS Cluster Configuration Reference
## Role-based Access Control
When provisioning an AKS cluster in the Rancher UI, RBAC cannot be disabled. If role-based access control is disabled for the cluster in AKS, the cluster cannot be registered or imported into Rancher.
When provisioning an AKS cluster in the Rancher UI, RBAC cannot be disabled. If role-based access control is disabled for the cluster in AKS, the cluster cannot be registered or imported into Rancher. In practice, this means that local accounts must be enabled in order to register an AKS cluster.
Rancher can configure member roles for AKS clusters in the same way as any other cluster. For more information, see the section on [role-based access control.](../../../how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/manage-role-based-access-control-rbac.md)