Create OperatorConfig for EDB when specified #1896
Merged
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.
Only allows for configuring replicas. The affinity and topologyspreadconstraints are hardcoded.
Current implementation assumes that CommonService CR only has one entry for operatorConfig, which is enough for CP4I.
Current implementation will result in the most recently reconciled CommonService CR's operatorConfig to take effect, i.e. overwrites will happen if there are multiple CommonService CRs. Intentional for now since will take too long to implement max size rule.
Needed to create a special branch for ODLM to include the new OperatorConfig APIs based off of the v1.19.0 release so that cs-operator can use the type without updating any other modules https://github.com/IBM/operand-deployment-lifecycle-manager/tree/operatorconfig-v1.19.0