k8s/apps
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

secrets

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files

10
velero/src/values.yaml
View File

@@ -337,9 +337,9 @@ configuration:
accessMode: ReadWrite
credential:
# name of the secret used by this backupStorageLocation.
name: secret-s3
name:
# name of key that contains the secret data to be used.
key: nas-s3
key:
# Additional provider-specific configuration. See link above
# for details of required/optional fields for your provider.
config:
@@ -371,9 +371,9 @@ configuration:
provider: aws
credential:
# name of the secret used by this volumeSnapshotLocation.
name: secret-s3
name:
# name of key that contains the secret data to be used.
key: nas-s3
key:
# Additional provider-specific configuration. See link above
# for details of required/optional fields for your provider.
config:
@@ -508,7 +508,7 @@ credentials:
name:
# Name of a pre-existing secret (if any) in the Velero namespace
# 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.
# 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.