Skip to content

EKS administration model that is not well-suited for “two-pizza teams

0

https://docs.hub.amazon..dev/learning/choosing-compute-platform/#elastic-container-service-for-kubernetes-eks (it doesn't allow me to add the link, so remove the additional . before dev, the link will work)

The above aws doc mentioned, for EKS, "Builder Tools does not recommend it for use by internal teams due to an administration model that is not well-suited for “two-pizza teams." I couldn't find any information on what does this mean. Does anyone know? Thanks so much!

asked a year ago191 views

1 Answer
0

The reference to EKS administration not being well-suited for "two-pizza teams" relates to the complexity and operational overhead of managing Kubernetes environments, which can be challenging for smaller teams.

Amazon EKS, while powerful and flexible, has a steeper learning curve compared to simpler container services like Amazon ECS. For small teams (traditionally defined as "two-pizza teams" - teams small enough to be fed with two pizzas), the operational burden of managing Kubernetes can be significant.

EKS requires more specialized knowledge about Kubernetes concepts and operations. Organizations typically adopt different models for providing Kubernetes capabilities:

  1. Templates as a Service - While offering a low barrier to entry, this approach becomes difficult to manage at scale, especially since development teams often neglect cluster upgrades.

  2. Cluster as a Service - Platform teams take more ownership of cluster management, keeping clusters updated and properly configured.

  3. Namespace as a Service - For more mature organizations, platform teams provide isolated namespaces with predefined resource quotas.

  4. Application-centric approach - Completely abstracts away the Kubernetes layer from developers.

For small teams without dedicated platform engineering resources, the operational effort required for EKS can be substantial. This is why AWS has introduced features like EKS Auto Mode, which automatically manages the setup, scaling, and maintenance of the Kubernetes control plane and worker nodes to reduce this operational burden.

In contrast, Amazon ECS is generally simpler to use with a lower learning curve, making it potentially more suitable for smaller teams that want to focus on application development rather than infrastructure management.
Sources
AWS re:Invent 2024 - Building production-grade resilient architectures with Amazon EKS | AWS re:Post
Under the hood: Amazon EKS Auto Mode | Containers
What is the different between ECS and EKS? | AWS re:Post
Choosing a modern application strategy - Choosing a modern application strategy

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.