All invenio k8s resources (deployment, service, etc) should have a unique name which can be assigned to a helm release. Currently, the resources of two different helm releases have the same name, which can cause conflicts by deploy two releases to the same namespace.
Possible solution:
Using the helm default naming convention function wich exist per default when charts created with: helm create...
{{/*
Expand the name of the chart.
*/}}
{{- define "invenio.name" -}}
{{- default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix "-" }}
{{- end }}
{{/*
Create a default fully qualified app name.
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec).
If release name contains chart name it will be used as a full name.
*/}}
{{- define "invenio.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 }}
All invenio k8s resources (deployment, service, etc) should have a unique name which can be assigned to a helm release. Currently, the resources of two different helm releases have the same name, which can cause conflicts by deploy two releases to the same namespace.
Possible solution:
Using the helm default naming convention function wich exist per default when charts created with:
helm create...