Option to override namespace

[Horkyze]

[EyalZilberblum]

helm command has an argument [--namespace] which can be used to install the chart in any namespace you desire. pay attention that helm cannot create the namespace, so you need to make sure it exists prior to the installation.

[vallard]

helm can create the namespace as of Feb 2020 (https://github.com/helm/helm/pull/7648). Run: helm -n <mynamespace> upgrade --install --create-namespace fluent fluent/fluentd -f values.yml

[simonliuxrex]

ran into issue installing into multiple namespaces.

$ helm upgrade -i fluent-bit helm/efk/fluent-bit --namespace kevin
Release "fluent-bit" does not exist. Installing it now.
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "fluent-bit" 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 "kevin": current value is "simon"

[assapir]

The need for namespaceOverride is for when one installs the chart as sub chart (or dependency) when we want the main application to be in one namespace, but fluentd/fluent-bit in anther one. If needed, I can try to create a PR for that.

[andreapigatto]

The need for namespaceOverride is for when one installs the chart as sub chart (or dependency) when we want the main application to be in one namespace, but fluentd/fluent-bit in anther one. If needed, I can try to create a PR for that.

Just run in similar issue using the chart as sub chart. Would be great to be able to override the value via values.yaml.

[Charly6596]

Another one here, due to our setup we need to override namespace