stack.basicstack.de/docs
CTO Agent 810d22f0a6 feat(monitoring): prometheus-backup → restic client-side encrypted (DEV-492)
Migrates the last plaintext-at-rest monitoring backup off rclone-sync
onto the same restic pipeline as loki/grafana/k8s-resources. Closes
the Hetzner Object Storage gap flagged in DEV-482 — no SSE-S3/SSE-KMS
means every object we push must be encrypted client-side.

- apps/monitoring/prometheus-backup-cronjob.yaml: pin the image to the
  Harbor mirror `harbor.basicstack.de/library/restic:0.17.3` (DEV-493)
  so the pull path matches the sibling CronJobs.
- docs/monitoring/restic-restore.md: append the DEV-492 drill entry —
  cold restic init, 8.017 GiB → 2.441 GiB stored, `restic check`
  clean, restore of `latest` into a scratch namespace, then
  `promtool tsdb list` + `promtool tsdb analyze` against all 19
  blocks (0 failed). Confirms the compaction-race mitigation
  (`--exclude wal/*`/`chunks_head/*` + accept exit 3) does not leave
  a corrupt snapshot. Also documents the DEV-492 Prometheus repo in
  the layout table + per-repo restore commands.
- apps/monitoring/README.md: point the restore section at all four
  repos and cite DEV-488 (loki/k8s) + DEV-492 (prometheus) drill
  entries.

Definition of done (DEV-492):
- backup ships client-side-encrypted to Hetzner:  (restic init
  succeeded on the manual run; snapshot 71420465 written)
- restore drill promtool tsdb analyze clean:  (19/19 blocks OK)
- OBSERVABILITY_BASELINE.md + apps/monitoring/README.md updated: 
- restic-password ownership documented:  (README shared-SealedSecret
  table already covered all four repos after this change)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-08-16 16:29:22 +00:00
..
monitoring feat(monitoring): prometheus-backup → restic client-side encrypted (DEV-492) 2026-08-16 16:29:22 +00:00
argocd.md Add comprehensive Argo CD documentation 2026-07-12 10:04:51 +00:00
README.md Add comprehensive Argo CD documentation 2026-07-12 10:04:51 +00:00

Documentation

This directory contains general documentation for the basicstack.de cluster and deployment processes.

Available Documentation

  • Argo CD - GitOps Platform: Comprehensive guide to the Argo CD deployment, including SSO login, managing applications, repository credential rotation, emergency recovery, and troubleshooting

Suggested Future Content

  • Architecture: Overall cluster architecture and design decisions
  • Deployment Guides: Step-by-step deployment procedures for specific scenarios
  • Troubleshooting: Common cluster-wide issues and solutions
  • Best Practices: Standards and conventions for this cluster
  • Operations Runbooks: Incident response and operational procedures
  • Disaster Recovery: Backup and restore procedures at the cluster level

Note

Application-specific documentation should live in the respective apps/<app-name>/ directories, not here. This directory is for cross-cutting concerns and cluster-wide documentation.