Allow setting a priorityClassName for DaemonSet check #646
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
|
@mtougeron thanks for the pr! this lgtm!! :) |
joshulyne
approved these changes
Sep 23, 2020
|
@integrii Thanks for merging this! How do I generate/trigger a new docker tag for this check? |
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 allows for you to optionally set a priorityClassName for the DaemonSet that is created in the check. This allows for preemption when some nodes are fully utilized.
While preemption isn't ideal, knowing the state of the synthetic checks & overall cluster health are a priority workload.