Skip to content

Conversation

developer67890
Copy link

This change adds a Helm Chart value singleNamespaceMode which configures to the operator to watch its deployed namespace if true.

While this could have been achieved by including the deployed namespace in the managedNamespaces list, it requires a user to specify a second time this namespace.

helm install elastic-operator ./eck-operator -n my-namespace --create-namespace \
  --set=managedNamespaces='{my-namespace}' \
...

This model is fragile and prone to mistyping or omissions. Other products have accomplished a similar feature by including something like clusterWide=false, which will result in the same behavior this PR achieves.

Changes:

  • add singleNamespaceMode value to values.yaml, including short comment explanation
  • if singleNamespaceMode = true, only include .Release.Namespace in the namespaces field of the Configmap.
  • update documentation for "Install the operator restricted to a single namespace"

Resolves #8828

Copy link

cla-checker-service bot commented Sep 29, 2025

❌ Author of the following commits did not sign a Contributor Agreement:
646dc1e, 56ee0ca, 13220a3

Please, read and sign the above mentioned agreement if you want to contribute to this project

@prodsecmachine
Copy link
Collaborator

prodsecmachine commented Sep 29, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@botelastic botelastic bot added the triage label Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ease Namespace Configuration
2 participants