feat: switch to backblaze
All checks were successful
lint-test-helm / lint-helm (pull_request) Successful in 19s
lint-test-helm / validate-kubeconform (pull_request) Successful in 16s
render-manifests / render-manifests (pull_request) Successful in 1m19s

This commit is contained in:
2026-05-04 20:41:55 -05:00
parent ecbe69acb4
commit ae042d09d0
2 changed files with 8 additions and 8 deletions

View File

@@ -32,12 +32,12 @@ spec:
data:
- secretKey: access
remoteRef:
key: /digital-ocean/home-infra/mariadb-backups
property: AWS_ACCESS_KEY_ID
key: /backblaze/home-infra/mariadb-backups
property: ACCESS_KEY_ID
- secretKey: secret
remoteRef:
key: /digital-ocean/home-infra/mariadb-backups
property: AWS_SECRET_ACCESS_KEY
key: /backblaze/home-infra/mariadb-backups
property: ACCESS_SECRET_KEY
---
apiVersion: external-secrets.io/v1

View File

@@ -151,7 +151,7 @@ mariadb-cluster:
physicalBackups:
- name: backup-external
schedule:
cron: "0 0 * * 0"
cron: "0 0 * * 6"
suspend: false
immediate: true
compression: gzip
@@ -159,10 +159,10 @@ mariadb-cluster:
successfulJobsHistoryLimit: 1
storage:
s3:
bucket: mariadb-backups-b230a2f5aecf080a4b372c08
bucket: mariadb-backups-6e3b78870f7af040
prefix: cl01tl/grimmory
endpoint: nyc3.digitaloceanspaces.com
region: us-east-1
endpoint: s3.us-east-005.backblazeb2.com
region: us-east-005
accessKeyIdSecretKeyRef:
name: grimmory-mariadb-cluster-backup-secret-external
key: access