-
Notifications
You must be signed in to change notification settings - Fork 341
Description
Is your feature request related to a problem? Please describe.
I'm generating helm charts that are generic, and when kics renders the manifest files it looks like its assuming the default namespace. It would be useful to be able to inject a namespace into the rendered manifest without having to define it in the helm charts, or input it via the values.yaml file.
The reason, is that I use ArgoCD, and it allow me to inject the namespace at the time the applications template manifest is rendered, thus removing the need for a helm chart template to include an input for the namespace. This is a default helm object, so its not something that has to be assumed in the templates.
Describe the solution you'd like
Provide a configuration option that would allow kics to inject a namespace into the helm generation process using the --namespace command line option for helm.
Describe alternatives you've considered
I have considered encoding a values.yaml entry for defining the namespace, but when this is rendered via ArgoCD, it causes already defined errors that block any further deployment of the application. Thus, this is not really an option for us.
Additional context
