672387e678
DEV-452. After the SQLite -> Postgres migration in DEV-451 the pangolin initial setup was redone, so the controller's stale bearer token was invalid. That was only half the problem: /api/v1/traefik-config is served exclusively by Pangolin's internal API (port 3001), not the external dashboard API (port 3000). Pointing a Bearer request at port 3000 always returned 401 because that path lives on the session-auth router. This has been the underlying cause of the controller's CrashLoopBackOff, not just the stale key. Changes: - pangolin-controller-api-key-sealed.yaml: reseal new bearer token (kubeseal against sealed-secrets-controller in kube-system, includes the Bearer prefix expected by the controller). - pangolin-controller-config.yaml: CONFIG_ENDPOINT now targets http://pangolin.pangolin.svc.cluster.local:3001/api/v1/traefik-config. - pangolin-deployment.yaml: Service now exposes port 3001 as the "internal" port so in-cluster clients (kube-controller) can reach it. Ingress still only routes / and /api to ports 3002/3000; port 3001 is not published to the internet. - pangolin-controller-deployment.yaml: replicas back to 1, dropped the temporary "scaled to 0" comment block. Co-Authored-By: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| argocd | ||
| basicstack-org | ||
| bookstack | ||
| directus | ||
| dozzle | ||
| forgejo | ||
| forgejo-runner | ||
| harbor | ||
| headlamp | ||
| opencloud | ||
| pangolin | ||
| paperclip | ||
| passbolt | ||
| platform-prod | ||
| pocket-id | ||
| stalwart | ||
| app-argocd.yaml | ||
| app-basicstack-org.yaml | ||
| app-bookstack.yaml | ||
| app-directus.yaml | ||
| app-dozzle.yaml | ||
| app-forgejo-runner.yaml | ||
| app-forgejo.yaml | ||
| app-harbor.yaml | ||
| app-headlamp.yaml | ||
| app-opencloud.yaml | ||
| app-pangolin.yaml | ||
| app-paperclip.yaml | ||
| app-passbolt.yaml | ||
| app-platform-prod.yaml | ||
| app-pocket-id.yaml | ||
| app-stalwart.yaml | ||
| ARGOCD-MIGRATION.md | ||
| README.md | ||
Applications
This directory contains deployment configurations for all applications running on the basicstack.de cluster.
ArgoCD Application Management
Each application has two types of files:
app-<name>.yaml: ArgoCD Application manifest that tells ArgoCD to sync the app subdirectory<name>/: Application-specific Kubernetes manifests and configuration
The app-*.yaml files are synced by ArgoCD and create/manage the corresponding Application resources.
Each application's manifests in its subdirectory are then synced by its Application resource.
Structure
Each application should have its own subdirectory containing:
- Kubernetes manifests: Deployment, StatefulSet, Service, ConfigMap, Secret definitions
- Helm values: If using Helm charts, include values.yaml files
- Configuration files: Application-specific configs (TOML, JSON, YAML)
- Documentation: README or guide specific to the application deployment
- Patches: Any kubectl patches or modifications needed
Example: Stalwart
The stalwart/ directory serves as a reference implementation, containing:
- Multiple deployment variants (basic, with OIDC, etc.)
- Helm values files
- Monitoring dashboard configurations
- Backup/restore procedures
- Operational documentation
Adding a New Application
- Create a new directory:
apps/<application-name>/ - Add your Kubernetes manifests
- Include a README.md explaining:
- What the application does
- How to deploy it
- Configuration options
- Troubleshooting steps
- Test the deployment in a dev environment
- Commit with a descriptive message
Naming Conventions
- Directory names: lowercase, hyphen-separated (e.g.,
my-app) - Manifest files: descriptive names indicating resource type (e.g.,
deployment.yaml,service.yaml) - Use consistent naming across applications