Michal.Wrobel/openbao-helm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

comment out the auto-unseal blocks

Browse source
This commit is contained in:
Clint Shryock 2018-12-03 16:08:20 -06:00
parent b70470d917
commit 001ff9450f
No known key found for this signature in database
GPG key ID: B7C8F9C70EC5CD29
1 changed files with 18 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
values.yaml
View file

@ -55,14 +55,15 @@ server:
path = "/vault/data"
}
# The GKMS keys must already exist, and the cluster must have a service
# account that is authorized to access GCP KMS, and ass
seal "gcpckms" {
project = "vault-helm-dev"
region = "global"
key_ring = "vault-helm"
crypto_key = "vault-init"
}
# Example configuration for using auto-unseal, using Google Cloud KMS. The
# GKMS keys must already exist, and the cluster must have a service account
# that is authorized to access GCP KMS.
# seal "gcpckms" {
# project = "vault-helm-dev"
# region = "global"
# key_ring = "vault-helm"
# crypto_key = "vault-init"
# }
# extraVolumes is a list of extra volumes to mount. These will be exposed
# to Vault in the path `/vault/userconfig/<name>/`. The value below is
@ -112,14 +113,15 @@ serverHA:
address = "HOST_IP:8500"
}
# The GKMS keys must already exist, and the cluster must have a service
# account that is authorized to access GCP KMS, and ass
seal "gcpckms" {
project = "vault-helm-dev"
region = "global"
key_ring = "vault-helm"
crypto_key = "vault-init"
}
# Example configuration for using auto-unseal, using Google Cloud KMS. The
# GKMS keys must already exist, and the cluster must have a service account
# that is authorized to access GCP KMS.
# seal "gcpckms" {
# project = "vault-helm-dev"
# region = "global"
# key_ring = "vault-helm"
# crypto_key = "vault-init"
# }
# extraVolumes is a list of extra volumes to mount. These will be exposed
# to Vault in the path `/vault/userconfig/<name>/`. The value below is