This commit is contained in:
Philip Haupt
2025-04-14 00:22:35 +02:00
parent bcb07c5d85
commit f66be53eb6
2 changed files with 9 additions and 28 deletions

View File

@@ -3450,19 +3450,6 @@ subjects:
namespace: velero namespace: velero
--- ---
apiVersion: v1 apiVersion: v1
data: null
kind: Secret
metadata:
labels:
app.kubernetes.io/instance: velero
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: velero
helm.sh/chart: velero-7.0.0
name: velero
namespace: velero
type: Opaque
---
apiVersion: v1
kind: Service kind: Service
metadata: metadata:
labels: labels:
@@ -3505,7 +3492,6 @@ spec:
template: template:
metadata: metadata:
annotations: annotations:
checksum/secret: b9754ca4d83dab2f2e3ce5d2f763c69ed92c2298dc2737084680716557250af3
prometheus.io/path: /metrics prometheus.io/path: /metrics
prometheus.io/port: "8085" prometheus.io/port: "8085"
prometheus.io/scrape: "true" prometheus.io/scrape: "true"
@@ -3588,7 +3574,7 @@ spec:
volumes: volumes:
- name: cloud-credentials - name: cloud-credentials
secret: secret:
secretName: velero secretName: secret-s3
- emptyDir: {} - emptyDir: {}
name: plugins name: plugins
- emptyDir: {} - emptyDir: {}
@@ -3611,7 +3597,6 @@ spec:
template: template:
metadata: metadata:
annotations: annotations:
checksum/secret: b9754ca4d83dab2f2e3ce5d2f763c69ed92c2298dc2737084680716557250af3
prometheus.io/path: /metrics prometheus.io/path: /metrics
prometheus.io/port: "8085" prometheus.io/port: "8085"
prometheus.io/scrape: "true" prometheus.io/scrape: "true"
@@ -3671,7 +3656,7 @@ spec:
volumes: volumes:
- name: cloud-credentials - name: cloud-credentials
secret: secret:
secretName: velero secretName: secret-s3
- hostPath: - hostPath:
path: /var/lib/kubelet/pods path: /var/lib/kubelet/pods
name: host-pods name: host-pods
@@ -3744,9 +3729,7 @@ spec:
region: home-nas region: home-nas
s3ForcePathStyle: "true" s3ForcePathStyle: "true"
s3Url: http://s3.home:9000 s3Url: http://s3.home:9000
credential: credential: null
key: nas-s3
name: secret-s3
default: true default: true
objectStorage: objectStorage:
bucket: kubernetes bucket: kubernetes
@@ -3765,7 +3748,5 @@ metadata:
spec: spec:
config: config:
region: home-nas region: home-nas
credential: credential: null
key: nas-s3
name: secret-s3
provider: aws provider: aws

View File

@@ -337,9 +337,9 @@ configuration:
accessMode: ReadWrite accessMode: ReadWrite
credential: credential:
# name of the secret used by this backupStorageLocation. # name of the secret used by this backupStorageLocation.
name: secret-s3 name:
# name of key that contains the secret data to be used. # name of key that contains the secret data to be used.
key: nas-s3 key:
# Additional provider-specific configuration. See link above # Additional provider-specific configuration. See link above
# for details of required/optional fields for your provider. # for details of required/optional fields for your provider.
config: config:
@@ -371,9 +371,9 @@ configuration:
provider: aws provider: aws
credential: credential:
# name of the secret used by this volumeSnapshotLocation. # name of the secret used by this volumeSnapshotLocation.
name: secret-s3 name:
# name of key that contains the secret data to be used. # name of key that contains the secret data to be used.
key: nas-s3 key:
# Additional provider-specific configuration. See link above # Additional provider-specific configuration. See link above
# for details of required/optional fields for your provider. # for details of required/optional fields for your provider.
config: config:
@@ -508,7 +508,7 @@ credentials:
name: name:
# Name of a pre-existing secret (if any) in the Velero namespace # Name of a pre-existing secret (if any) in the Velero namespace
# that should be used to get IAM account credentials. Optional. # that should be used to get IAM account credentials. Optional.
existingSecret: existingSecret: secret-s3
# Data to be stored in the Velero secret, if `useSecret` is true and `existingSecret` is empty. # Data to be stored in the Velero secret, if `useSecret` is true and `existingSecret` is empty.
# As of the current Velero release, Velero only uses one secret key/value at a time. # As of the current Velero release, Velero only uses one secret key/value at a time.
# The key must be named `cloud`, and the value corresponds to the entire content of your IAM credentials file. # The key must be named `cloud`, and the value corresponds to the entire content of your IAM credentials file.