Fill gaps from assistant conversations: clarify protected tier and node updates - #307
Open
mintlify[bot] wants to merge 2 commits into
Open
Fill gaps from assistant conversations: clarify protected tier and node updates#307mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
yaseenisolated
approved these changes
Aug 4, 2026
wesrobin
approved these changes
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies that the
compute_tiersetting governs preemption and consolidation only — it does not exempt instances from node maintenance events such as OS patches, kernel upgrades, or platform rollouts.Changes
scaling/scaling-apps.mdxunder Compute Tier.response_grace_perioddraining.min_replicas >= 2plus a suitableresponse_grace_periodto minimize disruption.Context
Recurring assistant conversations asked whether protected-tier apps are immune to node patches/updates. The existing docs only enumerated preemption and consolidation as interruption sources, leaving node lifecycle events ambiguous — the assistant had to walk back an incorrect claim in one thread. This closes that gap so readers can answer the question directly from the page.