Add Helm template validation for mutually exclusive namespace flags

[Copilot]

config.namespace and config.excludeNamespaces are mutually exclusive — the controller calls os.Exit(1) when both are set — but the chart previously rendered both args without complaint, producing a broken install.

Changes

• templates/deployment.yaml: Adds a fail guard at the top of the template that aborts helm install/helm upgrade with a clear error when both values are non-empty:

{{- if and .Values.config.namespace .Values.config.excludeNamespaces }}
{{- fail "config.namespace and config.excludeNamespaces are mutually exclusive and cannot both be set" }}
{{- end }}

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[Copilot]

Pull request overview

This PR adds Helm-side validation to prevent generating an invalid controller Deployment when both config.namespace and config.excludeNamespaces are set, matching the controller’s runtime constraint.

Changes:

• Add a Helm template fail guard to abort helm install/upgrade if config.namespace and config.excludeNamespaces are both non-empty.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.