Support specifying priority class for nifi pods #96
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
erdrix
approved these changes
May 13, 2022
Sure thing, done :) |
|
LGTM |
erdrix
added a commit
that referenced
this pull request
Aug 3, 2022
Support specifying priority class for nifi pods
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.
What's in this PR?
This pod adds
priorityClassNametoNodeConfigto support customizing the priority class of nifi nodes.Why?
Downtime due to k8s node terminations was prolonged due to the priority of nifi pods always being 0. This would result in nifi being the first pod stopped and the last pod rescheduled.
Additional context
Checklist
To Do