Add support for svclb pod PriorityClassName #10045
Merged
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.
Proposed Changes
Add support for svclb pod PriorityClassName
At this point I would prefer not to add another CLI flag to control the default priorityClassName, but you can override it on a per-service basis via an annotation. The annotation can be set to an empty value if svclb pods for that service should not have a priorityClassName set.
Types of Changes
enhancement
Verification
See linked issue
Testing
Linked Issues
priorityClassName
on ServiceLB daemonset. #10033User-Facing Change
Further Comments