Menu

We set maxUnavailable to zero, the platform team set a pod quota, and no release could start
📰

We set maxUnavailable to zero, the platform team set a pod quota, and no release could start

DEV Community: kubernetes·Sergey Shinder·3 days ago
#rTMPZ3FP
#devtokubernetes#devto#dev#quota#twenty
Long article (370 words) — no AI summary yet.
Reading 0:00
15s threshold

Our checkout service runs twenty replicas, and its rolling update has maxUnavailable set to zero and maxSurge at twenty five percent. Zero unavailable was a rule we were proud of: a release never takes capacity away. It adds five new pods, waits for them to be ready, then removes five old ones.

In October the platform team introduced resource quotas on every namespace, after one team's batch job had filled a cluster. To avoid arguments, each quota was set from what the namespace was actually running that week. Checkout got a limit of twenty pods and a CPU request total to match. Nothing changed on the day, because nothing new was created.

On Thursday we released a fix for a voucher bug. The deployment created its new ReplicaSet, the ReplicaSet tried to create five pods, and quota admission refused every one: exceeded quota, the namespace already had twenty pods.…

Continue reading — create a free account

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