https://rancher.com/ logo
Title
c

clean-painting-58815

06/28/2022, 9:32 PM
Hello, I just installed a brand new Rancher 2.6.5 on an EKS 1.22 cluster. When I go to the import cluster screen and attempt to import / register a EKS cluster, I see boxes to provide cloud credentials and I don't understand why. When I go to the "import generic cluster" option instead, I see the appropriate "agent environment var" settings and can click create to get the correct kubectl commands to run on one of my managed nodes and get it imported / registered. Is that the way it should be? I would have expected the EKS option to be worded the same way as the generic cluster option.
a

agreeable-waiter-30020

06/28/2022, 9:37 PM
If you import an EKS (or GKE, AKS) cluster, then you will have the option to manage the EKS config from Rancher similar to the way you can manage an EKS cluster created through Rancher. This management requires that you provide AWS credentials. If you don't care about managing the EKS config from Rancher, then you can import it as a generic cluster.
c

clean-painting-58815

06/28/2022, 9:47 PM
Thanks Donnie. I know that managing EKS requires that additional permissions be on the cluster before you run the kubectl to register the cluster, but the documentation doesn't mention anything about requiring cloud credentials that I can see. https://rancher.com/docs/rancher/v2.6/en/cluster-provisioning/registered-clusters/#registering-a-cluster
a

agreeable-waiter-30020

06/29/2022, 1:56 AM
In order to manage the EKS config, Rancher needs to be able to make API calls to AWS. That is why the creds are needed to import the cluster as and EKS cluster. If you just want to manage kubernetes (and not the EKS config) then no creds are needed.
­čĹŹ 1
c

clean-painting-58815

06/29/2022, 12:15 PM
Thanks Donnie, that helps to clarify what I'm seeing. I think this may be more of a documentation issue that needs a bit more clarity, Cheers!