Join us

Lesson learned while scaling Kubernetes cluster to 1000 pods in AWS EKS

Lesson learned while scaling Kubernetes cluster to 1000 pods in AWS EKS

The article discusses the challenges and lessons learned while scaling a Kubernetes cluster to 1000 pods in AWS EKS.

Some of the challenges include

  • AWS resource limits,
  • IP address exhaustion,
  • control plane performance issues,
  • workload calculations.
The article provides tips on workload calculation, choosing the right instance type, using Karpenter as the cluster auto-scaler, and tuning the Amazon CNI plugin.

Other considerations include scalability testing and EKS support for IPv6. The article aims to provide a frame of reference for scaling Kubernetes clusters, not the highest level of performance.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

Unsubscribe anytime. By subscribing, you share your email with @faun and accept our Terms & Privacy.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.

Join other developers and claim your FAUN.dev() account now!

Avatar

The FAUN

FAUN.dev()

@faun
The FAUN watches over the forest of developers. It roams between Kubernetes clusters, code caves, AI trails, and cloud canopies, gathering the signals that matter and clearing out the noise.
Developer Influence
3k

Influence

302k

Total Hits

3711

Posts