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

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

Browse Source 
Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com>
This commit is contained in:
Yiannis Triantafyllopoulos
2024-12-18 09:55:21 +00:00
committed by yiannistri
parent b9602b9af2
commit 4dd65ee2a2
2 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -35,7 +35,7 @@ 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.
AKS clusters can only be imported if local accounts are enabled. If a cluster is configured to use Microsoft Entra ID for authentication, Rancher will not be able to import the cluster 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.
@@ -295,10 +295,11 @@ This section lists some of the most common errors that may occur when importing
### AKS
#### Error: Getting static credential is not allowed because this cluster is set to disable local accounts.
- 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.
* 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
```
```sh
az aks update --resource-group <resource-group> --name <cluster-name> --enable-local-accounts
```

2
docs/reference-guides/cluster-configuration/rancher-server-configuration/aks-cluster-configuration.md
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. In practice, this means that local accounts must be enabled in order to register an AKS cluster.
When provisioning an AKS cluster in the Rancher UI, RBAC cannot be disabled. If RBAC is disabled in the AKS cluster, the cluster cannot be registered or imported into Rancher. In practice, this means that local accounts must be enabled in order to register or import 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)