Make rolling out AND replacing EKS clusters an easy, robust and reliable procedure. It will cover all your needs including creating new clusters to actually serve workloads in. It will also automatically give you: Disaster Recovery Proven upgrades (instead of "it might work" in-place upgrades) Robust code (used often, so faults come to light early and not two seconds to twelve) Up-to-date knowledge (because you don't let it go stale by having some magic long-lived process that nobody will remember a year from now) Cost-wise, having 100 EKS clusters (or 10000) is cheaper than having 1 outage (in most cases, considering a cluster should probably deliver more profit than $70). This does mean you need to take two other things into account: Automatic configuration based on references or shared data, we do this by setting the cluster secret in ArgoCD with some extra fields that are exposed in every ApplicationSet (this prevents you from hard-coding cluster-specific things in your manifests) Data portability or stateless clusters where your application state is persisted outside of the cluster. For every group of clusters (or cluster-of-clusters) we dedicate a separate AWS account for persistence, this means that even if you somehow lose all clusters, you can do a single `terraform apply` and everything is back in working order and ArgoCD fully reconciled in tens of minutes. Treat your clusters like cattle, just like you treat pods and worker nodes like cattle. More on reddit.com

Yes we have got it working in production. There were quite a few gotchas we found since we run a pretty big setup, over 10,000 pods. The HPA wasn't working but they have got that patched. Another thing to watch out for is IP limitation due to the worker instance nodes if you run a lot of pods. Where are you getting stuck at? More on reddit.com