Skip to content

Draft: Connection Draining and the Myth of the Zero-Downtime Deploy#49

Draft
singhsanjay12 wants to merge 1 commit into
mainfrom
ssingh1/connection-draining-zero-downtime-deploys
Draft

Draft: Connection Draining and the Myth of the Zero-Downtime Deploy#49
singhsanjay12 wants to merge 1 commit into
mainfrom
ssingh1/connection-draining-zero-downtime-deploys

Conversation

@singhsanjay12

Copy link
Copy Markdown
Owner

Draft blog post for review (merge later).

A rolling deploy is not zero-downtime by default. Without draining, every pod you terminate drops in-flight requests and races endpoint propagation. Here is the SIGTERM contract, the preStop hook, the readiness-before-exit ordering, and how proxies drain long-lived connections.

  • House style: hero SVG, styled code blocks, closing pull-quote.
  • Publish date is a placeholder (2026-04-27); adjust before publishing.
  • Cross-links only to already-merged posts.
  • Validated: combined build + tests pass (64 runs, 0 failures); 0 em dashes; SVG passes svg_test.

🤖 Generated with Claude Code

… Deploy

Placeholder publish date (2026-04-27); adjust before publishing. Cross-links only to already-merged posts.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant