Allow setting priorityClassName on pods #113
Merged
+7
−0
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.
I have a hardware device attached to my Home Assistant node, so it will only work on one particular node. To make sure that the scheduler makes room for HA (if other workloads have already been scheduled there), I created a priority class. I realised the template doesn't support this yet, so I've added an option.
If
priorityClassName
is set, this allows for a configuration where the scheduler evicts other pods and puts HA on the right node. Here's what that looks like for me (a snippet from myvalues.yaml
):Of course, there also needs to be a label on the node and the priority class needs to exist.