Homelabv4/scripts/vps-dns-failover/vps-dns-failover.service at a869a5a67f9134706744b26129d710361ab8aa7f - Homelabv4 - Gitea: Git with a cup of tea

gitea_admin/Homelabv4

mirror of https://gitlab.kube.huskypup.net/Scooby/Homelabv4.git synced 2026-08-20 23:16:49 +00:00

Files

T

Scooby Husky 7990f1fa47 Add VPS warm-standby/backup site (Phase 0-1b)

Foundation for a DR/backup path using an always-on VPS as a second
ArgoCD-managed cluster, plus DB/backup standardization work that fell
out of it:

- vps-standby ArgoCD cluster destination + AppProject, MinIO backup
  receiver, VPS bootstrap script (k3s, Netbird, cert-manager)
- Dual-site DNS failover watcher + home-IP DDNS CronJob, Cloudflare
  token moved out of git into Vault+ExternalSecret
- Nextcloud migrated from ad-hoc MariaDB to CNPG + redis-operator
  (matches n8n/Authentik/GitLab's backup-native pattern)
- Authentik's CNPG manifests moved into the actual ArgoCD-synced
  manifests/ path (were present but never wired into the sync path)
- Vault raft-snapshot CronJob, CNPG barmanObjectStore backups
  (Authentik/n8n/Nextcloud), Nextcloud file-PVC restic sync - all
  targeting the new VPS MinIO receiver

See VPS Warm-Standby plan doc for full design rationale.

2026-08-17 14:59:26 -05:00

11 lines

324 B

Desktop File

Raw Blame History

 [Unit]
 Description=VPS dual-site DNS failover check (Homelabv4 vps-standby)
 After=network-online.target
 Wants=network-online.target
 [Service]
 Type=oneshot
 ExecStart=/usr/local/bin/vps-dns-failover.sh
 # Deliberately no dependency on k3s/docker being up - this must keep working
 # even if the VPS's own cluster is unhealthy.