railiance-platform/helm/apps-pg-2-backup.yaml

apiVersion: postgresql.cnpg.io/v1
kind: ScheduledBackup
metadata:
  name: apps-pg-2-daily
  namespace: databases
  labels:
    cnpg.io/cluster: apps-pg-2
spec:
  schedule: "0 15 2 * * *"
  backupOwnerReference: self
  cluster:
    name: apps-pg-2
  immediate: true
  method: barmanObjectStore
Finish RPF-WP-0018; RPF-WP-0019 repository-complete RPF-WP-0018 closed: all seven tasks done. The provider-declaration finding was adopted upstream and its canonical form is the provider: block in tenancy.yaml; adaptive-pricing declined the standing co-signature and supplied typed tier minima instead, recorded in ADR-0002. Three corrections against our own output are recorded in the documents rather than edited away. RPF-WP-0019 T03 done (ceiling of three, memory binding, apps-pg-2 named as overflow, enforced by make apps-pg-verify-capacity). T01/T02 are repository-complete: backup target, retention, per-consumer connection limits, role timeouts and Burstable resources are declared in source and published in s3-consumer-interfaces 1.1.0 before rollout. They stay in progress because no live application, backup success or restore proof exists, and declared configuration is not a section 13 artifact. T04 waits on that window. apps-pg R reason corrected to say the target is declared-not-applied rather than absent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 2026-08-18 13:35:04 +02:00			`apiVersion: postgresql.cnpg.io/v1`
			`kind: ScheduledBackup`
			`metadata:`
			`name: apps-pg-2-daily`
			`namespace: databases`
			`labels:`
			`cnpg.io/cluster: apps-pg-2`
			`spec:`
			`schedule: "0 15 2 * * *"`
			`backupOwnerReference: self`
			`cluster:`
			`name: apps-pg-2`
			`immediate: true`
			`method: barmanObjectStore`