Skip to content

test(d3): deploy a deliberately broken gateway (revert right after) - #83

Merged
AlpNuhoglu merged 1 commit into
mainfrom
test/d3-broken-release
Oct 22, 2026
Merged

AlpNuhoglu merged 1 commit into
mainfrom
test/d3-broken-release

Conversation

@AlpNuhoglu

Copy link
Copy Markdown
Owner

⚠️ Deliberately broken — plan D3's test, to be reverted right after

The prod overlay gives the gateway a 17-character JWT_SECRET (a value in env overrides the Secret's from envFrom), so config.Validate refuses to start it in production.

Expected when merged

  • The deploy job's rollout for gateway makes no progress (CrashLoopBackOff), hits progressDeadlineSeconds (300 s), and deploy.sh redeploys the previous commit with its own manifests; the job ends red.
  • With maxUnavailable: 0 the old gateway pod is never removed: public requests keep answering 200 throughout (measured from outside).
  • The 5-minute wait inside one kubectl rollout status call outlives a token: the exec plugin should log a second token in that call.

Then a revert PR restores the normal state.

🤖 Generated with Claude Code

To be reverted right after. The prod overlay gives the gateway a
JWT_SECRET of 17 characters (a value in env overrides the Secret's from
envFrom), so config.Validate refuses to start it in production. Plan
D3's check: the deploy job must turn red and roll back to the previous
commit with its own manifests, and production must keep serving
throughout. The rollout waits for the 300 s progress deadline, which
also exercises token renewal inside one long kubectl call.

Plan: D3

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AlpNuhoglu
AlpNuhoglu merged commit 53e6a50 into main Oct 22, 2026
26 checks passed
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