pal-e-docs
Project not found.

Validation 71 — cnpg_scheduled_backup cron drift auto-resolved

validation-71-2026-04-26 Doc

validation pass
Project

Validation 71 — cnpg_scheduled_backup cron drift

Summary

Verdict: PASS. Issue #71 auto-resolved by tofu apply on 2026-04-26 (no PR required — was state-vs-source drift only).

Context

Issue #71 was filed during PR #70's post-merge validation when tofu plan showed full-manifest drift on kubernetes_manifest.cnpg_scheduled_backup: source terraform/cnpg.tf:177 had "0 0 2 * * *" (6-field with seconds) while terraform state held "0 2 * * *" (5-field).
The follow-up tofu apply later that day (after PR #70 merge) pushed the 6-field source value through. CNPG accepted it without coercion. State and live now match source.

Checks

  • Live spec verified. kubectl get scheduledbackup -n postgres pal-e-postgres-daily -o jsonpath='{.spec.schedule}' returns 0 0 2 * * * — matches source.
  • Backup running. kubectl get scheduledbackup -n postgres pal-e-postgres-daily shows LAST BACKUP 17h ago (last successful run within expected window).
  • Cluster healthy. kubectl get cluster.postgresql.cnpg.io -n postgres pal-e-postgres reports Cluster in healthy state. Primary pod pal-e-postgres-1 uptime 42d (no restart from this apply).
  • Plan clean. Post-apply tofu plan -lock=false -var-file=k3s.tfvars shows zero in-place updates on kubernetes_manifest.cnpg_scheduled_backup.
  • Forgejo issue: forgejo_admin/pal-e-services#71 (closed)
  • Triggering apply: 2026-04-26 post-PR-#70 follow-through
  • Companion: validation-69-2026-04-26 (CNPG computed_fields)