However, it is not really supported. RKE2 comes with its own images for the Kubernetes components, and while you CAN use those steps to use the eks-d binaries instead, it is not something we really recommend.
EKS-D was still in early access when that article was released, so the scripts probably don’t work with the current state of things and would need some tweaking.
11/29/2022, 1:04 PM
Thank you for the response/background!
Interesting.. so this documentation here : https://docs.ranchermanager.rancher.io/how-to-guides/new-user-guides/kubernetes-cluster-setup/rke2-for-rancher describes RKE2 being installed as a server so it appears that RKE2 is still being developed. And it needs to installed as a server where Rancher Management is installed as well as an agent for all clusters that Rancher needs to manage. Is that correct? Do you recommend RKE2 at all?
Managing EKS-D would be a prototype to see how it works, from what we understand it appears we can only import the EKS-D cluster per Article below and that was from 2022. It seems like you can import EKS-D following documentation but it is unclear.. it sounds like SUSE rancher has not tested this management of EKS-D since 2020 then?
EKS-D is just a standard way for Amazon to publish the artifacts that they use internally for EKS clusters. You can take those artifacts and have RKE2 use them instead of the artifacts (binaries) that it would normally use.
RKE2 is a Kubernetes distro that is still in active development, but has been stable for quite a while. We don’t actively support using EKS-D binaries though; that was just a proof of concept.
11/29/2022, 7:17 PM
Got it. So not great for production use cases. Thank you so much for your clarification!