9d1996051e
- Create the missing forgejo/platform-backup-data PVC that forgejo-backup references (20Gi hcloud-volumes-encrypted). - Record monitoring/backup-k8s-resources with a k3s-worker-2 nodeSelector (backup-storage PVC is local-path pinned there), lower memory request (128Mi) so it fits worker-2 pressure, and switch to alpine/k8s image (bitnami/kubectl is no longer resolvable). - Rewrite monitoring/backup-volumes to only back up grafana + loki co-located with backup-storage on k3s-worker-2. Prometheus data lives on k3s-worker-1 and is intentionally excluded here; a dedicated Prometheus data backup follows in a separate ticket. The three CronJobs previously left Pending/ContainerCreating pods that blocked the OS-update health guard in DEV-463. Co-Authored-By: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| forgejo-backup-cronjob.yaml | ||
| forgejo-deployment.yaml | ||
| forgejo-ingress.yaml | ||
| forgejo-postgres-secret-sealed.yaml | ||
| forgejo-postgres-service.yaml | ||
| forgejo-postgres-statefulset.yaml | ||
| forgejo-pvc.yaml | ||
| forgejo-service.yaml | ||
| platform-backup-data-pvc.yaml | ||