chore(ci): provide non-default namespace to Helm deployers

[DerekRoberts]

Provide non-default namespace to Helm deployments. Best practice, prevents GitHub alerts.

---

Thanks for the PR!

Deployments, as required, will be available below:

• Frontend
• Backend

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[Copilot]

Pull Request Overview

This PR adds an explicit namespace setting for both frontend and backend Helm deployments so they deploy into the non-default namespace specified by the Helm release.

• Added a namespace field in the frontend deployment template
• Added a namespace field in the backend deployment template

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

File	Description
charts/app/templates/frontend/templates/deployment.yaml	Added explicit namespace using {{ .Release.Namespace }}
charts/app/templates/backend/templates/deployment.yaml	Added explicit namespace using {{ .Release.Namespace }}

Comments suppressed due to low confidence (2)

charts/app/templates/frontend/templates/deployment.yaml:6

• Explicitly setting the namespace here is good practice. Please verify that using '{{ .Release.Namespace }}' consistently supports the overall deployment strategy.

namespace: {{ .Release.Namespace }}

charts/app/templates/backend/templates/deployment.yaml:6

• Explicitly setting the namespace here is good practice. Please verify that using '{{ .Release.Namespace }}' consistently supports the overall deployment strategy.

namespace: {{ .Release.Namespace }}