forked from validatedpatterns/multicloud-gitops
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathvalues-secret.yaml.template
More file actions
40 lines (38 loc) · 1.23 KB
/
values-secret.yaml.template
File metadata and controls
40 lines (38 loc) · 1.23 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# Secrets documentation can be found here:
# https://validatedpatterns.io/learn/secrets-management-in-the-validated-patterns-framework/
#
# A more formal description of this format can be found here:
# https://github.com/validatedpatterns/rhvp.cluster_utils/tree/main/roles/vault_utils#values-secret-file-format
version: "2.0"
# Ideally you NEVER COMMIT THESE VALUES TO GIT (although if all passwords are
# automatically generated inside the vault this should not really matter)
secrets:
- name: config-demo
vaultPrefixes:
- global
fields:
- name: secret
onMissingValue: generate
vaultPolicy: validatedPatternDefaultPolicy
# If you use clusterPools you will need to uncomment the following lines
#- name: aws
# fields:
# - name: aws_access_key_id
# ini_file: ~/.aws/credentials
# ini_section: default
# ini_key: aws_access_key_id
# - name: aws_secret_access_key
# ini_file: ~/.aws/credentials
# ini_key: aws_secret_access_key
#- name: publickey
# fields:
# - name: content
# path: ~/.ssh/id_rsa.pub
#- name: privatekey
# fields:
# - name: content
# path: ~/.ssh/id_rsa
#- name: openshiftPullSecret
# fields:
# - name: content
# path: ~/.pullsecret.json