You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an operator, I'd like to use the Helm release namespace for the different Kubernetes resources.
Detailed Description
Currently, the Helm chart defines the namespace used across the different templates as part of the values file. This works and ensures that all manifests are deployed at the same place.
However, we could also achieve this by using the built-in object and its subfield (.Release.Namespace). This would also make the chart more flexible, both from operator, as well as from a developer standpoint. Is there a specific reason that we derive the namespace from the values instead of the release?
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
The text was updated successfully, but these errors were encountered:
What would you like to be added (User Story)?
As an operator, I'd like to use the Helm release namespace for the different Kubernetes resources.
Detailed Description
Currently, the Helm chart defines the namespace used across the different templates as part of the values file. This works and ensures that all manifests are deployed at the same place.
However, we could also achieve this by using the built-in object and its subfield (
.Release.Namespace
). This would also make the chart more flexible, both from operator, as well as from a developer standpoint. Is there a specific reason that we derive the namespace from the values instead of the release?Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
The text was updated successfully, but these errors were encountered: