namespace support in helm chart

[prudnitskiy]

Description

A small PR enables namespaces for helm chart.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• CI/CD or infrastructure change

How Has This Been Tested?

Test deployment to the separate cluster

• Unit tests
• Integration tests
• Manual tests

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[Endevir]

Hi @prudnitskiy, thanks for your contribution!

Could you explain why it's necessary to specify the namespace manually in the resources?

Doesn't running helm install <release-name> <chart-name> --namespace <namespace-name> automatically deploy the resources into the specified namespace?

[prudnitskiy]

Hi @Endevir,

The namespace doesn't always work correctly if passed as argument. It is also important for ArgoCD, Flux and Kustomize users that pass namespace as a helm chart property. By default, Helm renders chart to the current namespace. This contribution does not change Helm chart behaviour for normal use but helps to use helm as an interim tool.

[jurim76]

Usually charts don't use "namespace" generally and flux "targetNamespace" works as expected