Skip to content

Allow ECK-Operator to easily watch deployed namespace #8830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
developer67890 wants to merge 3 commits into from
Closed

Allow ECK-Operator to easily watch deployed namespace #8830

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
646dc1e
Add singleNamespace mode value and logic
developer67890 Sep 29, 2025
56ee0ca
Update docs on single namespace deployment
developer67890 Sep 29, 2025
13220a3
Fix missed typo in README
developer67890 Sep 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion deploy/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,9 @@ helm install elastic-operator-crds ./eck-operator/charts/eck-operator-crds
# This step can be done by any user with full access to the my-namespace namespace.
helm install elastic-operator ./eck-operator -n my-namespace --create-namespace \
--set=installCRDs=false \
--set=managedNamespaces='{my-namespace}' \
--set=singleNamespaceMode=true \
--set=createClusterScopedResources=false \
--set=config.validateStorageClass=false \
--set=webhook.enabled=false
```

Expand Down
6 changes: 5 additions & 1 deletion deploy/eck-operator/templates/configmap.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,8 +67,12 @@ data:
{{- end }}
webhook-port: {{ .Values.webhook.port }}
{{- end }}
{{- with .Values.managedNamespaces }}
{{- if .Values.singleNamespaceMode }}
Copy link
Copy Markdown
Contributor

@barkbay barkbay Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we validate that managedNamespaces is not set if singleNamespaceMode is true?
Something along the lines of:

Suggested change
{{- if .Values.singleNamespaceMode }}
{{- if and .Values.singleNamespaceMode .Values.managedNamespaces }}
{{- fail "managedNamespaces should not be set when singleNamespaceMode is enabled" }}
{{- end }}
{{- if .Values.singleNamespaceMode }}

namespaces: [{{ .Release.Namespace }}]
{{- else }}
{{- with .Values.managedNamespaces }}
namespaces: [{{ join "," . }}]
{{- end }}
{{- end }}
operator-namespace: {{ .Release.Namespace }}
enable-leader-election: {{ .Values.config.enableLeaderElection }}
Expand Down
3 changes: 3 additions & 0 deletions deploy/eck-operator/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,9 @@ volumes: []
# createClusterScopedResources determines whether cluster-scoped resources (ClusterRoles, ClusterRoleBindings) should be created.
createClusterScopedResources: true

# singleNamespaceMode will set the operator to only watch its deployed namespace
singleNamespaceMode: false

# Automount API credentials for the Service Account into the pod.
automountServiceAccountToken: true

Expand Down