- Replace Gitea deployment with GitHub redirect
- Use Traefik Middleware for 301 redirect to github.com/mayne0213
- Keep TLS certificate for gitea0213.kro.kr
- Replace GitHub redirect with actual Gitea server
- SQLite database (no CNPG dependency)
- local-path StorageClass (no Longhorn dependency)
- Manual secret creation (no Vault dependency)
- Ingress at gitea0213.kro.kr
- Add metallb.universe.tf/allow-shared-ip annotation back to gitea SSH service
- This allows MetalLB to assign VIP and fix ArgoCD health status (Progressing → Healthy)
- Service will get 10.0.0.101 from MetalLB IPAddressPool
- Remove argocd/ and helm-values/ subdirectories
- Move files to parent directory (argocd.yaml, helm-values.yaml)
- Update helm valueFiles paths in ArgoCD Applications
- Remove CreateNamespace=true from all applications
- Namespace creation now handled by namespace.yaml with Goldilocks labels
- Add namespace.yaml with goldilocks.fairwinds.com/enabled label
- Enable VPA recommendations for all applications
- Update kustomization.yaml to include namespace resources
- Fix namespace names to match actual usage (umami -> analytics)
- Change database host to postgresql-cnpg-rw.postgresql-cnpg.svc.cluster.local
- Change database user from postgres to bluemayne
- Database password remains Po87345364! (same as before)
- Gitea data has been migrated to CNPG successfully
Set passwordMode to initialOnlyDoNotUpdate to prevent Gitea from forcing
password changes on every pod restart. This resolves the issue where users
were continuously prompted to update their password, causing ArgoCD
authentication failures.
- Use correct key: deploymentStrategy instead of deployment.strategy
- Set type to Recreate to prevent leveldb lock conflicts
- This will resolve OutOfSync issue
- Change repoURL from infrastructure.git to applications.git
- Consolidate all gitea resources in applications repository
- Remove dependency on infrastructure repository
