From 05f0101684dee0ed29c62c59011eabb4763f5f54 Mon Sep 17 00:00:00 2001 From: CTO Agent Date: Sat, 8 Aug 2026 11:20:22 +0000 Subject: [PATCH] chore(pangolin): Scale pangolin-controller to 0 pending API key re-issuance 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 --- apps/pangolin/pangolin-controller-deployment.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/apps/pangolin/pangolin-controller-deployment.yaml b/apps/pangolin/pangolin-controller-deployment.yaml index 7aa8683..4aa6756 100644 --- a/apps/pangolin/pangolin-controller-deployment.yaml +++ b/apps/pangolin/pangolin-controller-deployment.yaml @@ -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: