Correct the service-level min-instances runbook flag#3744
Draft
anth-volk wants to merge 1 commit into
Draft
Conversation
The runbook documented gcloud run services update --min-instances 1 as the service-level warm-capacity command, but that flag sets the REVISION-level minimum — the exact per-tag warm-instance cost bomb the same section warns against. The service-level flag is --min (recent gcloud only; the YAML-replace fallback and its Cloud Resource Manager API prerequisite are now documented). Caught while executing the runbook for the Stage 3 exit gates. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3744 +/- ##
=======================================
Coverage 79.89% 79.89%
=======================================
Files 70 70
Lines 4332 4332
Branches 807 807
=======================================
Hits 3461 3461
Misses 652 652
Partials 219 219 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
1 participant
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
Executing the Stage 3 post-merge runbook surfaced that its command was wrong:
gcloud run services update --min-instances 1sets the revision-level minimum — the exact per-tag warm-16Gi cost bomb the surrounding section warns against. The service-level flag is--min(verified against current Cloud Run docs).The runbook now documents the correct flag, the gcloud-version caveat (older SDKs lack
--min; the YAML-replace fallback setsrun.googleapis.com/minScaleon service metadata and requires the Cloud Resource Manager API), and records that the step was executed 2026-07-08 via that fallback.Docs + changelog only; no runtime changes. (The actual production service already carries the correct service-level annotation — verified: template minScale absent, service metadata minScale=1.)
🤖 Generated with Claude Code