Managing multiple EKS clusters: why cluster #3 is the wall
From the source: SUSE BlogDo the arithmetic before you read the rest of this. Count the people on your team who need access to a cluster. Multiply by the number of clusters you run. That result is how many access decisions somebody is maintaining by hand today. Now add one cluster and run it again. The jump between those […]
Read the full story on SUSE BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in Containers & Kubernetes
OpenShift vs managed Kubernetes (EKS/AKS/GKE) for regulated workloads
For teams in financial services, government or healthcare: which did you choose and what tipped it: compliance evidence, support, cost or skills?
How many Kubernetes clusters do you run, and how do you keep upgrades sane?
Fleet size, managed vs self-managed, and the tooling that keeps version upgrades from becoming a quarterly fire drill.
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from SUSE
Recent updates from SUSE, so you can tell whether this is a one-off or part of a pattern.
More in Containers & Kubernetes
What other companies in Containers & Kubernetes are doing. The category page shows who’s active, side by side.

