Kubernetes backup and restore

Responsibility boundaries, component-consistent backups, and evidence-based restore verification.

Short glossary
  • Helm release: an installed and independently managed resource set from one chart.
  • Secret object: a Kubernetes resource referenced for sensitive values; the delivery charts do not own the values themselves.
  • PersistentVolumeClaim (PVC): a storage request used by a bundled data component.
  • NetworkPolicy: rules governing permitted network connections for application Pods.
  • Container Storage Interface (CSI) and Container Network Interface (CNI) capabilities are provided by the customer cluster.

Backup and restore

External-store backup, HA, failover, retention, and RPO/RTO are customer responsibilities. Bundled mode requires encrypted off-cluster, component-consistent backups and a restore drill in a clean isolated target.

  • PostgreSQL: consistent logical dump; Kafka: quiesced single-broker backup; ClickHouse: consistent backup interface; Redis: persistence-safe AOF/RDB copy after sync
  • Record the backup identity, retention, encryption, and restore result without credentials or customer data
  • Accept restore only after the original application marker is read through each component's client protocol on fresh storage identities
  • Application uninstall does not own data; data release uninstall removes controllers and Services but retains PVCs
WarningA Bound PVC, an archive, or a zero exit code is not restore evidence. Numerical RPO/RTO requires repeated proof on the customer's CSI and backup target.