Update community-operator chart to support having a namespace override #277
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).