Current documentation instructs users that want to deploy ECK Operator in a restricted manner to do the following:

helm install elastic-operator elastic/eck-operator -n elastic-system --create-namespace \
  --set=installCRDs=false \
  --set=managedNamespaces='{namespace-a, namespace-b}' \
  --set=createClusterScopedResources=false \
  --set=webhook.enabled=false \
  --set=config.validateStorageClass=false

This mode of configuration requires hard-coding namespaces via--set=managedNamespaces='{namespace-a, namespace-b}'. In a multi-tenancy model where applications have ECK-Operator as a subchart, this method is inconvenient and fragile as it requires installers to specify the namespace for every installation in addition to the one for Helm.

Proposal to include a setting such as singleNamespaceMode that would configure the configmap with .Release.Namespace. This would allow the chart to be deployable in a more automated fashion with less bespoke configuration.