Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlpNuhoglu merged 1 commit into from
Oct 22, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions deployments/k8s/overlays/prod/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,20 @@ patches:
value:
name: TRUSTED_PROXIES
value: 10.42.0.0/16
# D3 TEST, reverted right after: a deliberately broken release. A value in
# env overrides the one from envFrom (the Secret), so the gateway gets a
# JWT_SECRET shorter than 32 characters and config.Validate refuses to
# start it. The deploy job must turn red, roll back to the previous
# commit, and production must keep serving throughout.
- target:
kind: Deployment
name: gateway
patch: |-
- op: add
path: /spec/template/spec/containers/0/env/-
value:
name: JWT_SECRET
value: d3-test-too-short
# The public API name (C1). Its DNS record is an A record only, without
# the Cloudflare proxy: the cluster is IPv4-only (finding #81), and a proxy
# would end TLS at Cloudflare and hide the client's address from the
Expand Down
Loading