From 6d9e405126ee8730b3fced86c782372502fe4a3c Mon Sep 17 00:00:00 2001 From: Ruben Hensen Date: Wed, 21 Oct 2026 15:25:16 +0200 Subject: [PATCH] Point Velero and the NAS services back at 192.168.1.99 Reverts 8c2bd89. The NAS had fallen back to a DHCP address (.10), which also moved the UniFi controller it hosts away from where the gateway and access points inform, and left the Longhorn backup target at nfs://192.168.1.99 unreachable. It now has 192.168.1.99 set statically in DSM again, so everything that pointed at .99 works without changes. --- backup-testing/README.md | 2 +- backup-testing/test-velero-backup.sh | 4 ++-- nas/service.yaml | 2 +- velero/nas-svc.yaml | 2 +- velero/velero-helm.yaml | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/backup-testing/README.md b/backup-testing/README.md index aa13d68..2fc8781 100644 --- a/backup-testing/README.md +++ b/backup-testing/README.md @@ -72,7 +72,7 @@ This will: | `--s3-secret-key KEY` | S3/MinIO secret key | (required) | | `--s3-bucket BUCKET` | S3 bucket containing backups | `velero-backups` | | `--s3-region REGION` | S3 region | `minio` | -| `--s3-url URL` | S3 endpoint URL | `http://192.168.1.10:9000` | +| `--s3-url URL` | S3 endpoint URL | `http://192.168.1.99:9000` | | `--original-namespace NS` | Namespace in the original backup | (required) | | `--test-namespace NS` | Namespace for restoration | `default` | | `--original-domain DOMAIN` | Domain to replace in ingresses | `hensen.io` | diff --git a/backup-testing/test-velero-backup.sh b/backup-testing/test-velero-backup.sh index 5120c72..55f4ed8 100755 --- a/backup-testing/test-velero-backup.sh +++ b/backup-testing/test-velero-backup.sh @@ -14,7 +14,7 @@ set -e BACKUP_NAME="" S3_BUCKET="velero-backups" S3_REGION="minio" -S3_URL="http://192.168.1.10:9000" +S3_URL="http://192.168.1.99:9000" S3_ACCESS_KEY="" S3_SECRET_KEY="" ORIGINAL_NAMESPACE="" @@ -91,7 +91,7 @@ while [[ $# -gt 0 ]]; do echo " --backup-name NAME Name of the Velero backup to restore" echo " --s3-bucket BUCKET S3 bucket containing backups (default: velero-backups)" echo " --s3-region REGION S3 region (default: minio)" - echo " --s3-url URL S3 endpoint URL (default: http://192.168.1.10:9000)" + echo " --s3-url URL S3 endpoint URL (default: http://192.168.1.99:9000)" echo " --s3-access-key KEY S3 access key" echo " --s3-secret-key KEY S3 secret key" echo " --original-namespace NS Namespace in the original backup" diff --git a/nas/service.yaml b/nas/service.yaml index 0679608..16c1343 100644 --- a/nas/service.yaml +++ b/nas/service.yaml @@ -4,7 +4,7 @@ metadata: name: nas-external spec: type: ExternalName - externalName: 192.168.1.10 + externalName: 192.168.1.99 ports: - name: nas-5000 protocol: TCP diff --git a/velero/nas-svc.yaml b/velero/nas-svc.yaml index dfff4b9..de49f87 100644 --- a/velero/nas-svc.yaml +++ b/velero/nas-svc.yaml @@ -4,7 +4,7 @@ metadata: name: nas-minio-external spec: type: ExternalName - externalName: 192.168.1.10 + externalName: 192.168.1.99 ports: - port: 9000 protocol: TCP \ No newline at end of file diff --git a/velero/velero-helm.yaml b/velero/velero-helm.yaml index da874e9..abe86ff 100644 --- a/velero/velero-helm.yaml +++ b/velero/velero-helm.yaml @@ -30,7 +30,7 @@ spec: config: region: minio s3ForcePathStyle: true - s3Url: http://192.168.1.10:9000 + s3Url: http://192.168.1.99:9000 insecureSkipTLSVerify: "true" volumeSnapshotLocation: - name: default