From 1c70d8a9d2c2d6866d47d3a7051437b4fb21d2d3 Mon Sep 17 00:00:00 2001 From: aphorise Date: Mon, 15 May 2023 14:53:49 +0200 Subject: [PATCH] values.yaml updated to include explicit cluster_name 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 --- values.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/values.yaml b/values.yaml index 9e35ac8bc..e804a49c5 100644 --- a/values.yaml +++ b/values.yaml @@ -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