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 b1680431c6 feat(monitoring): pull restic image from Harbor mirror (DEV-493) 
Point the three monitoring restic CronJobs at the Harbor-hosted
mirror at harbor.basicstack.de/library/restic:0.17.3 so the backup
pipeline is not gated by Docker Hub throttling or upstream retag.

- Mirrored docker.io/restic/restic:0.17.3 into the public
  `library` project via a one-shot crane copy Job. Digest in
  Harbor matches the upstream index (sha256:8f5a62b4…).
- Updated the three CronJobs
  (backup-loki-restic, backup-grafana-restic,
  backup-k8s-resources) to pull from Harbor.
- Documented the tag-bump procedure in
  docs/monitoring/restic-restore.md (§ Tag-bump procedure) and
  pointed the restore-drill pod at the same Harbor image so the
  restore round-trip stays image-consistent with the writers.

Refs: [DEV-493](/DEV/issues/DEV-493), parent [DEV-482](/DEV/issues/DEV-482).

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-08-16 16:20:06 +00:00
..
monitoring feat(monitoring): pull restic image from Harbor mirror (DEV-493) 2026-08-16 16:20:06 +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.