Allow scheduling constraints for operator-ui pods #2326
Merged
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
pratheekrebala
requested review from
sdudoladov,
Jan-M,
FxKu,
jopadi,
idanovinda and
hughcapet
as code owners
|
Would be great to have this especially in a multi arch environment. |
|
I'm really looking forward to have these parameters in the UI panel |
|
any update on this please ? @sdudoladov @Jan-M @FxKu @jopadi @idanovinda @hughcapet |
|
👍 |
1 similar comment
|
👍 |
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.
This PR is a simple update to the
postgres-operator-uichart allows the following scheduling constraints to theoperator-uipods:affinitynodeSelectortolerationspriorityClassNameTo clarify, this change only affects the
operator-uipods themselves and isn't a change to the actual UI.This has come up before in the following issues:
#1921
#1885