helm chart does not allow for a different namespace

[draganm]

Current chart is just a single YAML without any variables.
It forces creation of doppler-operator-system, which is not the default behaviour of most other helm charts from other projects.

[nmanoogian]

Hi @draganm, thanks for calling this out 👍

To confirm, you would have expected the operator namespace to be configurable as a variable in the chart?

[draganm]

yes, and also this not to be part of the chart (currently in templates/all.yaml):

apiVersion: v1
kind: Namespace
metadata:
  labels:
    control-plane: controller-manager
  name: doppler-operator-system

it's wrong on many levels ...

• helm will create a namespace for you if you pass the --create-namespace parameter
• it completely ignores the namespace parameter that helm will pass
• it makes hashicorp/helm terraform provider fail when namespace parameter is passed, even if the value is doppler-operator-system

[nmanoogian]

Gotcha, thanks again for the feedback! We'll keep you posted here with any updates.

[adambozson]

+1 This is unusual behaviour. Currently the installation namespace needs to be different to doppler-operator-system or the install fails. I suggest removing the Namespace resource and setting the metadata.namespace value in other resources to either:

• {{ .Release.Namespace }}, or
• {{ .Values.namespace }} with an associated namespace key/value pair in values.yaml

[emmeowzing]

I presently don't know how to install these Helm charts on my cluster without downloading the tarballs and removing this namespace object. You could also do a lookup function to see if it exists?