Repository navigation
Revert "test(d3): deploy a deliberately broken gateway" - #84
Merged
Merged
Conversation
The test is over. Merged as 53e6a50, the broken release did what plan D3 asks for: the gateway's new pod never started (config.Validate), the rollout hit its 300 s progress deadline, deploy.sh redeployed e0defae with its own manifests (the JWT_SECRET override gone, the broken ReplicaSet at 0) and the job ended red. The old gateway pod served throughout and never restarted. This reverts commit e8a333d (merged in 53e6a50). Plan: D3 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Reverts the deliberately broken release from #83 (commit
e8a333d, merged as53e6a50).deployments/k8sis again identical toe0defae, the last good release.What the test showed (plan D3)
53e6a50: the new gateway pod never started (config.Validate:JWT_SECRETtoo short);rollout statusreportedexceeded its progress deadlineafter exactly 5 min (01:01:16 → 01:06:04 UTC).deploy.shthen redeployede0defaewith its own manifests: all 8 Deployments rolled out, smoke test passed, the job ended red (rolled back: e0defae… runs again; 53e6a50… is not deployed).JWT_SECREToverride is gone from the Deployment.kubectl rollout statuswas not needed: the watch stream authenticated once and stayed open after the token's expiry.This merge deploys normally (the healthy path).
🤖 Generated with Claude Code