mirror of
https://gitlab.kube.huskypup.net/Scooby/Homelabv4.git
synced 2026-08-21 05:26:49 +00:00
Scooby Husky
6e054a46b6
CNPG's barmanObjectStore.serverName defaults to the externalClusters[]
entry's own .name field ('home-backup', an arbitrary label I chose) -
NOT the actual source Postgres cluster's name. Home's backup: block
(on the real pg-authentik/pg-n8n/pg-nextcloud Clusters) defaults
serverName to its own metadata.name instead. Without an explicit
override these two disagree, so recovery searches the object store
under the wrong server-name prefix and finds nothing - 'no target
backup found', confirmed live even after the ScheduledBackup fix
produced real, completed base backups.
78 lines
2.7 KiB
YAML
78 lines
2.7 KiB
YAML
---
|
|
# CNPG "replica cluster" - continuously replays WAL shipped from home's
|
|
# pg-authentik cluster (infrastructure/authentik/manifests/cnpg-cluster.yaml)
|
|
# via VPS MinIO's cnpg-backups/pg-authentik bucket path. Unlike Vault's
|
|
# raft-restore CronJob (Vault has no native continuous-replication-into-
|
|
# object-store feature), CNPG's replica-cluster mode is a first-class
|
|
# built-in mechanism - no custom restore scripting needed, matches the
|
|
# plan's intent directly.
|
|
#
|
|
# While spec.replica.enabled is true, this cluster is a read-only standby
|
|
# in continuous recovery - the -rw service exists but is NOT writable
|
|
# (same "nothing accepts writes in normal operation" discipline as Vault/
|
|
# Gitea). Promoting it to a real writable primary during an actual
|
|
# incident is a deliberate manual step:
|
|
# kubectl -n authentik patch cluster pg-authentik --type merge \
|
|
# -p '{"spec":{"replica":{"enabled":false}}}'
|
|
# then scale the authentik Deployment(s) up from 0.
|
|
#
|
|
# vps-minio-secret is a plain Secret copied here manually (kubectl, not
|
|
# git) from the vps-minio-root-secret in the minio namespace - this
|
|
# cluster has no Vault/ESO of its own:
|
|
# kubectl -n authentik create secret generic vps-minio-secret \
|
|
# --from-literal=accesskey=<vps minio root user> \
|
|
# --from-literal=secretkey=<vps minio root password>
|
|
apiVersion: postgresql.cnpg.io/v1
|
|
kind: Cluster
|
|
metadata:
|
|
name: pg-authentik
|
|
namespace: authentik
|
|
spec:
|
|
imageName: ghcr.io/cloudnative-pg/postgresql:16
|
|
instances: 1
|
|
|
|
resources:
|
|
requests:
|
|
memory: "256Mi"
|
|
cpu: "25m"
|
|
limits:
|
|
memory: "1Gi"
|
|
cpu: "250m"
|
|
|
|
storage:
|
|
size: 5Gi
|
|
storageClass: local-path
|
|
|
|
bootstrap:
|
|
recovery:
|
|
source: home-backup
|
|
|
|
externalClusters:
|
|
- name: home-backup
|
|
barmanObjectStore:
|
|
# serverName defaults to the externalClusters[].name ("home-backup")
|
|
# here, NOT the source Postgres cluster's actual name - but home's
|
|
# barmanObjectStore backup: block (on the pg-authentik Cluster
|
|
# itself) defaults serverName to its own metadata.name
|
|
# ("pg-authentik"). Without this override, recovery looks for
|
|
# backups under the wrong server-name prefix and finds none -
|
|
# "no target backup found" despite the backup genuinely existing
|
|
# (confirmed live 2026-08-18).
|
|
serverName: pg-authentik
|
|
destinationPath: s3://cnpg-backups/pg-authentik
|
|
endpointURL: http://vps-minio.minio.svc.cluster.local:9000
|
|
s3Credentials:
|
|
accessKeyId:
|
|
name: vps-minio-secret
|
|
key: accesskey
|
|
secretAccessKey:
|
|
name: vps-minio-secret
|
|
key: secretkey
|
|
|
|
replica:
|
|
enabled: true
|
|
source: home-backup
|
|
|
|
monitoring:
|
|
enablePodMonitor: false # no Prometheus on the VPS cluster
|