https://rancher.com/ logo
Title
d

dry-vr-36164

03/13/2023, 11:07 AM
Hi everyone, Is there any way to rename the cluster on which we install the rancher. Currently it is shown as
local
. I need to rename it to something else.
b

big-hydrogen-97240

03/13/2023, 12:37 PM
No, the local cluster is special and should keep that name.
d

dry-vr-36164

03/13/2023, 12:38 PM
Yes, the local cluster is one of our envs i.e
dev
and would want to change name to make sense for devs.
a

agreeable-oil-87482

03/13/2023, 2:03 PM
You have other applications than Rancher running in the
local
cluster?
d

dry-vr-36164

03/13/2023, 5:32 PM
Yes, we have our dev environment running on that EKS cluster.
We have 4 env: 1. dev ( rancher is installed on this cluster and other envs cluster are imported here) 2. qa 3. stage 4. prod
a

agreeable-oil-87482

03/13/2023, 5:40 PM
Don't coexist general purpose workloads on the same cluster rancher is installed on.
d

dry-vr-36164

03/13/2023, 5:58 PM
ok @agreeable-oil-87482, thanks for info, let me discuss this with team.
btw @agreeable-oil-87482 do you know what this error could be while importing an exsiting cluster into rancher?
a

agreeable-oil-87482

03/13/2023, 6:33 PM
Check the permissions you've associated with the account you've used to import the cluster
d

dry-vr-36164

03/13/2023, 6:35 PM
ok, will.... Also do you have guide which we can follow steps to import an EKS cluster? most probably just need to know permissions will be needed in that credentials so that it can import successfully.
b

big-hydrogen-97240

03/13/2023, 6:52 PM
Credentials are listed here: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-clusters-in[…]/set-up-clusters-from-hosted-kubernetes-providers/eks These are for creating EKS clusters. You could probably get away with a subset of these permissions for importing, but not sure which ones.
1