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> |
||
|---|---|---|
| .. | ||
| .gitkeep | ||
| namespace.yaml | ||
| pangolin-config.yaml | ||
| pangolin-controller-api-key-sealed.yaml | ||
| pangolin-controller-config.yaml | ||
| pangolin-controller-deployment.yaml | ||
| pangolin-controller-rbac.yaml | ||
| pangolin-controller-service.yaml | ||
| pangolin-deployment.yaml | ||
| pangolin-paperclip-configuration-guide-community.md | ||
| pangolin-postgres-secrets-sealed.yaml | ||
| pangolin-secrets-sealed.yaml | ||
| postgres.yaml | ||