DSYNHD-85: Add option for priority class references #201
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
…s for SOLR/transform-+sync-services - disruption budgets like existing ACS PDB only if replicas > 1 - disruption budgets relevant for best effort pre-emption handling + availability if priority class causes pod to be pre-empted during scheduling
AFaust
force-pushed
the
DSNYHD-85-OptionalPriorityClasses
branch
from
7a28dd6 to
bbc7c00
Compare
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 adds the option to specify priority class reference for any pods. It also adds pod disruption budgets for deployments / stateful sets that may run with more than one replica to ensure that pod pre-emption (due to priority class) and other constellations potentially triggering pod eviction at least attempt to keep service/availability uninterupted with one pod instance.