Two Vault Instances from Helm in one K8s cluster

sdmattheww · November 22, 2022, 3:26pm

Hi All,
I’ve installed Vault in my kubernetes cluster and am trying to install the same chart in a different namespace from helm. I receive this error

Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRoleBinding "vault-server-binding" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "vault2": current value is "vault"

Is it possible to change the value of the ClusterRoleBinding in the helm chart?

maxb · November 22, 2022, 7:43pm

All the objects the chart creates, get a name that starts with the string from this template:

github.com

hashicorp/vault-helm/blob/c13151a6ac18765f42a05524362946fae16e8a3f/templates/_helpers.tpl#L7-L18


      
          {{- define "vault.fullname" -}}
          {{- if .Values.fullnameOverride -}}
          {{- .Values.fullnameOverride | trunc 63 | trimSuffix "-" -}}
          {{- else -}}
          {{- $name := default .Chart.Name .Values.nameOverride -}}
          {{- if contains $name .Release.Name -}}
          {{- .Release.Name | trunc 63 | trimSuffix "-" -}}
          {{- else -}}
          {{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" -}}
          {{- end -}}
          {{- end -}}
          {{- end -}}

i.e.:

You can change the Helm release name to something other than vault
You can set nameOverride in Helm values
You can set fullnameOverride in Helm values

depending on exactly what behaviour you’re looking for.