Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setting priorityClassName on pods #113

Merged
merged 1 commit into from
Mar 2, 2025

Conversation

Javex
Copy link
Contributor

@Javex Javex commented Mar 2, 2025

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 my values.yaml):

priorityClassName: node-priority

nodeSelector:
  zigbee: "true"

Of course, there also needs to be a label on the node and the priority class needs to exist.

@pajikos
Copy link
Owner

pajikos commented Mar 2, 2025

Thank you @Javex

@pajikos pajikos merged commit 25bba46 into pajikos:main Mar 2, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants