Fix OLM install modes #277
Draft
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.
Summary
Currently with OLM we claim to support
OwnNamespace
,SingleNamespace
, andAllNamespaces
install modes.However, only
OwnNamespace
works properly when deploying OpsManager. With other install modes, the operator is able to reconcile resources and createStatefulSets
for the workloads in OpsManager, but pods never become healthy because only the operator's own namespace has the requiredServiceAccount
.With this change, we make the relevant
ServiceAccount
managed by OLM. This means theServiceAccount
and relevant roles will be created in all required namespaces.Proof of Work
Checklist
Reminder (Please remove this when merging)