basicstack/stack.basicstack.de
2
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions
stack.basicstack.de/docs
History
CTO Agent 49b724439b docs(monitoring): add restic restore runbook + first drill log (DEV-488) 
- Cover credentials projection via scratch ns + monitoring-s3-backup
  copy, per-repo restore commands (loki / k8s-resources / grafana),
  repo self-check + source-parity flow, cleanup, and rotation.
- Record first drill (2026-08-16): loki snapshot 97092888 and
  k8s-resources snapshot 9b0155cf restored; sha256 parity vs live
  loki-storage-encrypted PVC confirmed for all 4 files; cluster.yaml
  sanity-checked. Outcome: PASS.
- Next drill target: 2026-11-16 (quarterly); include restic/grafana
  once its first CronJob run has produced >= 1 snapshot.

Unblocks retirement of the legacy backup-volumes CronJob (DEV-489).

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-08-16 15:47:45 +00:00
..
monitoring docs(monitoring): add restic restore runbook + first drill log (DEV-488) 2026-08-16 15:47:45 +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

README.md

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.