fix: Fix Cluster CR schema - use barmanObjectStore instead of b2
Some checks failed
Deploy Cluster / Terraform (push) Successful in 35s
Deploy Cluster / Ansible (push) Has been cancelled

This commit is contained in:
2026-03-26 00:33:04 +00:00
parent 3ea28e525f
commit 5fa2b411ee

View File

@@ -14,7 +14,6 @@ spec:
storage: storage:
storageClass: local-path storageClass: local-path
size: 50Gi size: 50Gi
resizeStorageStorageClassName: local-path
resources: resources:
requests: requests:
@@ -26,28 +25,41 @@ spec:
bootstrap: bootstrap:
recovery: recovery:
externalClusters: source: b2-backup
- name: b2-backup
s3Compatible: externalClusters:
bucket: HetznerTerra - name: b2-backup
region: us-east-005 barmanObjectStore:
endpoint: s3.us-east-005.backblazeb2.com bucketName: HetznerTerra
prefix: rancher-backups/ region: us-east-005
credentials: endpoint: https://s3.us-east-005.backblazeb2.com
name: b2-credentials s3Compatible:
accessKey: B2_ACCOUNT_ID enabled: true
secretKey: B2_APPLICATION_KEY credentials:
accessKeyIdSecret:
name: b2-credentials
key: B2_ACCOUNT_ID
secretAccessKeySecret:
name: b2-credentials
key: B2_APPLICATION_KEY
backupPath: rancher-backups/
backup: backup:
b2: barmanObjectStore:
bucket: HetznerTerra bucketName: HetznerTerra
region: us-east-005 region: us-east-005
endpoint: s3.us-east-005.backblazeb2.com endpoint: https://s3.us-east-005.backblazeb2.com
prefix: rancher-backups/ s3Compatible:
enabled: true
credentials: credentials:
name: b2-credentials accessKeyIdSecret:
accessKey: B2_ACCOUNT_ID name: b2-credentials
secretKey: B2_APPLICATION_KEY key: B2_ACCOUNT_ID
secretAccessKeySecret:
name: b2-credentials
key: B2_APPLICATION_KEY
backupPath: rancher-backups/
walPath: rancher-backups/wals
retentionPolicy: keep14 retentionPolicy: keep14
serviceAccountTemplate: serviceAccountTemplate: