ApiCore

4 Commits

Include renames

Author	SHA1	Message	Date
Nick SzaunigandClaude Opus 5.5	2359970f48	feat(k8s): daily pg_dump backup of the database Backend Image / build-and-push (push) Successful in 2m43s Details Frontend Image / build-and-push (push) Successful in 2m53s Details CronJob apicore-db-backup dumps the database to the Storage Box (StorageClass smb-backup, SMB 3.1.1 with seal). Keeps 14 daily and 8 weekly dumps. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-10-12 02:04:28 +02:00
Nick SzaunigandClaude Opus 5.5	cde817845e	chore(k8s): drop CPU and memory requests Backend Image / build-and-push (push) Successful in 3m9s Details Frontend Image / build-and-push (push) Canceled after 2m1s Details Requests are set to an explicit 0 instead of being removed, because Kubernetes defaults a missing request to the limit, which would reserve even more. Limits stay as an upper bound. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-10-10 04:08:07 +02:00
Nick SzaunigandClaude Opus 5.5	910ba804a6	chore(k8s): pin postgres to 18.6-alpine Backend Image / build-and-push (push) Successful in 3m12s Details Frontend Image / build-and-push (push) Successful in 3m7s Details The floating 18-alpine tag with IfNotPresent kept an old 18.x image cached on the nodes, so minor releases never reached the cluster. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-10-10 01:55:03 +02:00
Nick Szaunig	80890a5fc3	feat: PostgreSQL als StatefulSet im Kubernetes-Cluster deployen Backend Image / build-and-push (push) Successful in 3m8s Details Frontend Image / build-and-push (push) Successful in 2m54s Details Architektur-Entscheidung geaendert: PostgreSQL laeuft jetzt selbst im Cluster statt auf einer bestehenden externen Instanz. Neu: deploy/k8s/postgres/ mit StatefulSet (postgres:18-alpine, volumeClaimTemplates, pg_isready-Probes), headless Service (apicore-postgres) und Secret-Vorlage. Backend-DATABASE_URL zeigt auf den neuen In-Cluster-Service. CLAUDE.md/ARCHITECTURE.md aktualisiert: Backup-Verantwortung liegt jetzt beim Projekt, nicht mehr beim externen Cluster-/DBA-Betrieb (Backup-CronJob als offener Punkt in TASKS.md ergaenzt).	2026-08-26 17:43:49 +02:00