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

values.yaml updated to include explicit cluster_name

Browse source 
Setting an explicit cluster_name as part of the cluster roll-out / configuration is required without which a undesirable behavior arises where the reported Prometheus label does not correctly contain the cluster name - eg (at present):

vault_core_replication_dr_primary{cluster="",host="vault-2"} 0
This commit is contained in:
aphorise 2023-05-15 14:53:49 +02:00 committed by GitHub
parent 14585a1331
commit 1c70d8a9d2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
values.yaml
View file

@ -3,6 +3,10 @@
# Available parameters and their default values for the Vault chart.
# Set cluster name instead of having it auto-generated.
# examples may include: "vault1-gke-uswest", "vault2-eks-useast", etc.
cluster_name: ""
global:
# enabled is the master enabled switch. Setting this to true or false
# will enable or disable all the components within this chart by default.
@ -834,6 +838,7 @@ server:
# https://www.vaultproject.io/docs/platform/k8s/helm/run#protecting-sensitive-vault-configurations
config: |
ui = true
cluster_name = {{ .Values.cluster_name | default (printf "%s-k8s" (include "vault.name" .)) | quote }}
listener "tcp" {
tls_disable = 1