Menu

Amazon EKS: A successful rolling deployment doesn't guarantee zero downtime

Reddit r/kubernetes·u/rahulsharma_rks31·6 days ago
#WMeV1hgo
Reading 0:00
15s threshold

One thing I learned while working with Amazon EKS: A successful deployment doesn't always mean a reliable application.

When working with Kubernetes on AWS, it's easy to focus on getting deployments running, configuring CI/CD pipelines, and achieving successful rolling updates.

But production reliability goes beyond that.

One scenario worth paying attention to is node failure or node rotation.

Even if your application has multiple replicas and rolling deployments are configured correctly, you can still experience downtime if all replicas are scheduled on the same worker node.

A few Kubernetes configurations can help reduce this risk:

PodDisruptionBudget (PDB): Helps maintain minimum application availability during voluntary disruptions.

Topology Spread Constraints: Distributes replicas across different nodes or availability zones.

Pod Anti-Affinity: Helps prevent replicas from being scheduled on the same node.

Readiness Probes: Ensures traffic is sent only to pods that are ready to serve…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.