Importing Kubernetes Clusters
You can import an existing Kubernetes cluster and then manage it using Rancher. Keep in mind that editing your Kubernetes cluster (for example: adding/removing nodes, upgrading Kubernetes cluster version and changing Kubernetes component parameters) still has to be done outside of Rancher.
- If your existing Kubernetes cluster already has a
cluster-adminrole defined, you must have this
cluster-adminprivilege to import the cluster into Rancher. In order to apply the privilege, you need to run
kubectl create clusterrolebinding cluster-admin-binding --clusterrole cluster-admin --user [USER_ACCOUNT]before running the
kubectlcommand to import the cluster.
- By default, GKE users are not given this privilege, so you will need to run the command before importing GKE clusters. To learn more about GKE RBAC, please click here.
From the Clusters page, click Add Cluster.
Enter a Cluster Name.
Use Member Roles to configure user authorization for the cluster.
- Click Add Member to add users that can access the cluster.
- Use the Role drop-down to set permissions for each user.
The prerequisite for
cluster-adminprivileges is shown (see Prerequisites above), including an example command to fulfil the prerequisite.
kubectlcommand to your clipboard and run it on a node where kubeconfig is configured to point to the cluster you want to import. If you are unsure it is configured correctly, run
kubectl get nodesto verify before running the command shown in Rancher .
If you are using self signed certificates, you will receive the message
certificate signed by unknown authority. To work around this validation, copy the command starting with
curldisplayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import.
When you finish running the command(s) on your node, click Done.
- Your cluster is created and assigned a state of Pending. Rancher is deploying resources to manage your cluster.
- You can access your cluster after its state is updated to Active.
- Active clusters are assigned two Projects
Default(containing the namespace
System(containing the namespaces
kube-system, if present).
Note: You can not re-import a cluster that is currently active in a Rancher setup.