fixed case where, no ready label is defined, but node is unscheduable #1162
Conversation
This file contains hidden or 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
arminfelder
requested review from
CyberDem0n,
FxKu,
Jan-M,
RafiaSabih,
avaczi,
erthalion and
sdudoladov
as code owners
FxKu
reviewed
Oct 18, 2020
FxKu
reviewed
Oct 27, 2020
Member
|
👍 |
1 similar comment
Member
|
👍 |
Member
|
@arminfelder thanks for the contribution :) |
PetterSa
pushed a commit
to PetterSa/postgres-operator
that referenced
this pull request
Nov 19, 2020
…zalando#1162) * fixed case where, no ready label is defined, but node is unscheduable
PetterSa
added a commit
to PetterSa/postgres-operator
that referenced
this pull request
Nov 19, 2020
…heduable (zalando#1162)" This reverts commit e62852a.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
in case there is no ready label defined, an unschedulable should make a node not ready