You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
│ Error: Unable to continue with install: Namespace "k6-testing" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "k6-operator"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "k6-testing"
│
│ with module.k6.helm_release.k6_operator,
│ on ../../modules/k6/main.tf line 7, in resource "helm_release" "k6_operator":
│ 7: resource "helm_release" "k6_operator" {
The reason for this is that the helm chart currently doesn't utilize create_namespace provided by Helm but instead it creates it's own Namespace object
{{- if .Values.namespace.create }}
apiVersion: v1
kind: Namespace
metadata:
name: {{- include "k6-operator.namespace" . }}
labels:
app.kubernetes.io/name: {{ include "k6-operator.fullname" . }}
control-plane: "controller-manager"
{{- with .Values.customLabels }}
{{- toYaml . | nindent 4 }}
{{- end }}
annotations:
{{- include "k6-operator.customAnnotations" . | default "" | nindent 4 }}
{{- end }}
This can of course be worked around by setting
set {
name = "namespace.create"
value = "false"
}
It would be nice if the helm standard 'create_namespace` could be used instead tho.
We are using the helm chart from terraform as follows:
Now this fails with
The reason for this is that the helm chart currently doesn't utilize
create_namespace
provided by Helm but instead it creates it's own Namespace objectThis can of course be worked around by setting
It would be nice if the helm standard 'create_namespace` could be used instead tho.
Somewhat related: helm/helm#2853
Helm chart version (if applicable)
3.10.1
The text was updated successfully, but these errors were encountered: