We are building a top level "solution" helm chart that has several subchart dependencies, the community-operator helm chart being one. We want to have the subchart be installed within a specific namespace that we can specify in the top level solution chart.
Currently the community-operator helm chart has its namespace set to the Release namespace. This pull request updates the templates such that an "operator.namespaceOverride" value can be set which then installs the chart into that namespace. The proper namespaces for the database and service accounts are also configured if that value is set unless they are explicity set to something else such as the service account database namespace.
This has been tested as
a standalone installation of the chart with no namespace override
a standalone installation of the chart with operator.namespaceOverride set
a subchart with no namespace override
a subchart with operator.namespaceOverride set
When the operator.namespaceOverride is not set, there are no changes to the existing functionality.
All Submissions:
[x] Have you opened an Issue before filing this PR?
Closes #276
We are building a top level "solution" helm chart that has several subchart dependencies, the community-operator helm chart being one. We want to have the subchart be installed within a specific namespace that we can specify in the top level solution chart.
Currently the community-operator helm chart has its namespace set to the Release namespace. This pull request updates the templates such that an "operator.namespaceOverride" value can be set which then installs the chart into that namespace. The proper namespaces for the database and service accounts are also configured if that value is set unless they are explicity set to something else such as the service account database namespace.
This has been tested as
When the operator.namespaceOverride is not set, there are no changes to the existing functionality.
All Submissions:
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).