Allow namespace override for the objects in the Helm chart

[NR4l3rt0]

Is your feature request related to a problem? Please describe.
Well, it is not a problem in itself, but a kind of inconvenience. We just need to be able to override the namespace field on the resources the Chart provides.

We are using this tool since a long time, and we had to relate to do wrappers in parent charts or using extra tools/command flags (Helm, Helmfile,etc...); so that we can segment the cluster appropriately.
I think this is an issue affecting more users than us (as I can see here: #360 ) and at the same time I don't think it would be a major change.

Describe the solution you'd like
I have thought about implementing it as other code bases do, just adding a value variable and including it on the templates that use namespaced objects. In this case: ServiceAccount, Deployment, ClusterRoleBinding (subject section) and VerticalPodAutoscaler.

In fact I did a Pull Request already trying to help in the process so that you could understand me better: #395

Describe alternatives you've considered
I didn't consider other alternative, since they appeared to be wrappers instead of tackling the resources themselves. And they could be tricker to automate.

Additional context
I have tried to render those files and applied them in my local minikube cluster so that you see the differences:

• Kubernetes replicator from master:

kubernetes-replicator-master.yaml.txt

• Kubernetes replicator from branch with no overrides:

kubernetes-replicator-chg-noover.yaml.txt

• Kubernetes replicator from branch overriding namespace:

kubernetes-replicator-chg-yesover.yaml.txt

• Kubernetes replicator with namespace override and vpa enabled:

kubernetes-replicator-chg-yesover-vpa.yaml.txt

Please, let me know if you would be interested in discussing this, or if you would have any doubts regarding the implementation. Your understanding and feedback will be very welcomed.

Thanks for your time,