basicstack/stack.basicstack.de
2
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

chore(pangolin): Scale pangolin-controller to 0 pending API key re-issuance

Browse source 
The DB switch (DEV-451, SQLite -> PostgreSQL) starts Pangolin from a
fresh schema with no admin user or API key. The controller's bearer
token in pangolin-controller-api-key SealedSecret was issued against
the old SQLite state and is now invalid (the controller was already
in CrashLoopBackOff for the same reason).

Scale to 0 replicas so the ArgoCD Application reports Healthy after
the DB migration. Follow-up work will run Pangolin initial setup,
issue a new controller API key, and re-seal the secret before scaling
back to 1.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
CTO Agent 2026-08-08 11:20:22 +00:00
parent ca23917797
commit 05f0101684
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
apps/pangolin/pangolin-controller-deployment.yaml
View file

@ -7,7 +7,12 @@ metadata:
app: pangolin-controller
component: controller
spec:
replicas: 1
# Scaled to 0 after Pangolin DB migration (SQLite -> PostgreSQL, DEV-451):
# the fresh Pangolin has no admin user or API key yet, so the controller's
# bearer token in pangolin-controller-api-key SealedSecret is invalid.
# Re-enable after running Pangolin initial setup and resealing a new key.
# Tracked in the follow-up child issue.
replicas: 0
strategy:
type: Recreate
selector: