This message was deleted.
# generala
adamant-kite-43734
03/13/2023, 11:07 AMThis message was deleted.
b
big-hydrogen-97240
03/13/2023, 12:37 PMNo, the local cluster is special and should keep that name.
d
dry-vr-36164
03/13/2023, 12:38 PMYes, the local cluster is one of our envs i.e
deva
agreeable-oil-87482
03/13/2023, 2:03 PMYou have other applications than Rancher running in the
locald
dry-vr-36164
03/13/2023, 5:32 PMYes, we have our dev environment running on that EKS cluster.
dry-vr-36164
03/13/2023, 5:33 PMWe 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 PMDon't coexist general purpose workloads on the same cluster rancher is installed on.
d
dry-vr-36164
03/13/2023, 5:58 PMok @agreeable-oil-87482, thanks for info, let me discuss this with team.
dry-vr-36164
03/13/2023, 5:59 PMbtw @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 PMCheck the permissions you've associated with the account you've used to import the cluster
d
dry-vr-36164
03/13/2023, 6:35 PMok, 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 PMCredentials 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
63 Views