{
  "id": 20400560,
  "title": "We set maxUnavailable to zero, the platform team set a pod quota, and no release could start",
  "url": "https://urgent.news/2026/11/17/we-set-maxunavailable-to-zero-the-platform-team-set-a-pod-quota-and",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-17T07:52:15.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/sergey_shinder_ab2d943365/we-set-maxunavailable-to-zero-the-platform-team-set-a-pod-quota-and-no-release-could-start-1aef"
  },
  "original_language": "en",
  "account": "Our checkout service runs 20 replicas, with rolling updates set to allow for a maximum of zero unavailable pods and a maximum surge of 25%. This rule was considered a priority to ensure releases never consumed capacity. In October, the platform team introduced resource quotas for each namespace, after a team's batch job filled the cluster. To prevent conflicts, each quota was determined by the actual running pods that week.\n\nCheckout received a limit of 20 pods and a CPU request that matched. No changes were made on the day, as nothing was created. On Thursday, a fix for a voucher bug was deployed. The new ReplicaSet attempted to create five pods, but the quota admission refused each one, stating that the namespace already had 20 pods. With maxUnavailable at zero, the deployment couldn't remove an old pod until a new one was ready, and no new pod could exist without removing an old one. Neither side could progress.\n\nThe rollout timed out after 10 minutes, reporting a failure in the pipeline. The issue was traced back to the new ReplicaSet's events, where a FailedCreate error was logged. Unfortunately, this error was often overlooked during releases, and it took over an hour to identify. The voucher fix was delayed by two hours after the quota was manually increased.\n\nTwo settings, each intended to ensure release safety, ultimately prevented releases from starting. Neither team could claim responsibility for the combined issue. As a result, quotas are now calculated based on each deployment's replicas plus its surge, rather than the current cluster state. The platform repository now computes this from deployment manifests, and the pipeline checks quota availability before allowing a rollout to start. Any failures include the warning events for the new ReplicaSet, providing immediate visibility into the reason for rejection. Sergey Shinder emphasized that steady-state configurations are not suitable for environments that constantly require changes.",
  "summary": "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…",
  "key_points": [
    "Checkout service set maxUnavailable to zero for zero unavailable pods",
    "Platform team introduced resource quotas for each namespace",
    "Quota rejection caused rollout timeout and delayed voucher fix"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}