Possibility to add strategy and topologySpreadConstraints to the operator #1840
+17
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
karloramone
force-pushed
the
operator-deployment-chart
branch
from
6f6ddfc
to
784ef1d
Compare
csatib02
approved these changes
Nov 5, 2024
Signed-off-by: karloramone <[email protected]>
…tor chart Signed-off-by: karloramone <[email protected]>
Signed-off-by: karloramone <[email protected]>
Signed-off-by: karloramone <[email protected]>
karloramone
force-pushed
the
operator-deployment-chart
branch
from
08e5209
to
633276f
Compare
|
Thanks @csatib02, I did it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If you have two datacenters and you would like to deploy two replicas of the operator in each, you can't do that cause there is no possibility to modify topologySpreadConstraints of the operator deployment. The only way to assure two pods running in each datacenters is to run three replicas with the podAntiAffinity.
If you have a three node cluster you are not able to run three replicas with podAntiAffinity on the hostname topology key.
The problem is in the default strategy is configured to add the fourth replica before removing the old one. Because of the mentioned configuration above this is not possible and pod stays in pending state.
This fixes those two examples.
There is also one typo on the README.md that I noticed and fixed.