eks-distro VS eks-anywhere

EKS Anywhere builds on the strengths of Amazon EKS Distro, the same open-source distribution of Kubernetes that is used by Amazon EKS on the cloud, thus fostering consistency and compatibility between clusters both on AWS as well as on-premises.

yes im aware of bmctl. however you dont have control over the kubernetes distro that's running.

is there anything similar to https://github.com/aws/eks-distro ?

EKS-A focuses on cluster management for HA environments. By default we use 3 etcd nodes, 2 control plane nodes, and 3 worker nodes. It uses cilium as the default CNI and Cluster API controllers for continual cluster state management. It has some optional configuration for a flux controller and OIDC authentication but it doesn't add default services or workloads. EKS-A also uses EKS Distro which is the open source Kubernetes distribution we run in hosted EKS.

I'd suggest move from rancher to EKS Anywhere and the respective Cluster API providers... Self-managed node pools on top of bottlerocket can be established using common terraform-aws-eks module, otherwise.

There are plenty of vendor specific bugs, like no EBS in [EKS Fargate](https://github.com/aws/containers-roadmap/issues/1113), and settling a Kubernetes cluster on top of Bottlerocket and [EKS Anywhere](https://github.com/aws/eks-anywhere), on your own is somewhat impossible.

> It has no init system.

Apologies that I can't link directly to the "--init" flag but docker actually does have an init, it's just (err, was?) compiled into the binary: https://docs.docker.com/engine/reference/commandline/run/#op...

My recollection is that it either adopted, or inspired, https://github.com/Yelp/dumb-init#readme which folks used to put into their Dockerfile as the init system back in the day

Folks (ahem, I'm looking at you, eks-anywhere[0]) who bundle systemd into a docker container are gravely misguided, and the ones which do so for the ability to launch sshd alongside the actual container's main process are truly, truly lost

0: https://github.com/aws/eks-anywhere/issues/838#issuecomment-...

EKS anywhere looks like an adventure - https://anywhere.eks.amazonaws.com

That brings us to the end of this walkthrough. Thank you very much for reading and I hope you will give EKS Anywhere a spin. The complete documentation is available here. If you are interested in contributing, please open an issue or pull request on the EKS Anywhere GitHub repo. Let me know your thoughts in the comments below. If you have more questions, feel free to reach out to me on LinkedIn or Twitter.

EKS Engineer here. This is something we have lots of thoughts about and want to make better in EKS on AWS.

For EKS Anywhere, you can configure your cluster with OIDC auth today, and IAM auth is coming very soon. https://github.com/aws/eks-anywhere/issues/90

Not yet but it's a request we've heard from beta testers. Would love to hear what you need in a GitHub issue so we can prioritize additional providers. https://github.com/aws/eks-anywhere/issues