This message was deleted.
# amazon
a
This message was deleted.
r
At present you can't create a EKS-A cluster using Rancher.
You could import a cluster created using EKS-A into Rancher and then have access to the cluster dashboard/explorer and the ability to install addons etc using Rancher.
At present having a combined EKS-A management cluster and Rancher Manager cluster would be problematic at present as both use Cluster API. You could potentially work around this but there are some downside currently....but we are looking at making that better.
There is still a lot of value to be gained from importing cluster into Rancher.
You could potentially use EKS-D without EKS-A (some people have done with with vanilla cluster api) but the story is the same, you'd need to import the cluster into Rancher.
h
I see, How easily would it be to convert a cluster configuration running in rancher into EKS fully managed? I saw some support for interfacing with the EKS API, but I am assuming I would need to jump through more hoops than if I was to develop and test a cluster on an on prem-EKS anywhere environment, then deploy to a production in EKS fully managed?
r
Would you be able to clarify what you mean by "EKS fully managed"? Do you mean an EKS cluster running in AWS Cloud?
h
yes sorry, running in the AWS cloud and not on prem with EKS anywhere
r
In Rancher there is support for creating new EKS clusters, and also importing existing EKS clusters (that you can then manage).
h
Gotcha
s
To reiterate, you can run Rancher on EKS, Deploy additional EKS clusters from Rancher, and import other EKS clusters such as EKS-Anywhere on premise or on AWS Sno* devices, etc. and manage it all from Rancher, including the EKS cluster hosting the Rancher pods. Here's Rancher Setup on EKS across 3 availability zones from the AWS Marketplace. https://aws.amazon.com/marketplace/pp/prodview-go7ent7goo5ae SUSE Doc on this solution: https://documentation.suse.com/trd/kubernetes/single-html/gs_rancher_aws-marketplace/
👍 1