Reduced CPU requests to prevent node-agent scheduling failures:
- code-server: 100m → 50m (actual usage ~5m)
- kubernetes-dashboard metrics-scraper: 100m → 50m (actual usage minimal)
This optimization frees up 100m CPU on worker-node-2, allowing
Velero node-agent (30m request) to be scheduled successfully.
Worker-node-2 CPU allocation before: 840m/1000m (84%)
Worker-node-2 CPU allocation after: 730m/1000m (73%)
- Added ingress.yaml for code-server, kubernetes-dashboard, and umami
- Updated kustomization files to include ingress resources
- Migrated from centralized ingress management to per-app architecture
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
- Docusaurus builds index.html at /intro/ instead of root
- Add redirect from root (/) to /intro/ to fix 403 Forbidden error
- Update try_files fallback to use /intro/index.html
- Change git clone from infrastructure.git to applications.git
- This matches the ArgoCD Application configuration
- Fixes 'No such file or directory' error in initContainer
- Change cp -r build/* /build/ to cp -r build/. /build/
- This ensures all files and directories (including hidden files) are copied
- Fixes 403 Forbidden error caused by missing index.html in nginx root
