Skip to content

docs: explain traffic drain gap after SIGTERM - #451

Open
jackowfish wants to merge 2 commits into
mainfrom
jack/health-check-drain-docs
Open

docs: explain traffic drain gap after SIGTERM#451
jackowfish wants to merge 2 commits into
mainfrom
jack/health-check-drain-docs

Conversation

@jackowfish

@jackowfishjackowfish commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Description

Our zero-downtime docs told web services to fail the health check on SIGTERM and then close the server, which reads as "stop accepting connections right away."

I added a short section explaining the underlying mechanism of EndpointSlice updates.

Routing updates in the background, so requests keep landing for at least 1 to 5 seconds after the health check starts failing, and SIGTERM has no fixed ordering against that.

The guidance now says to keep serving through a drain window while draining what you already hold.

@mintlify

mintlifyBot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

ProjectStatusPreviewUpdated (UTC)
porter🟢 ReadyView PreviewAug 11, 2026, 3:41 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for freeto 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

@jackowfish