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

Feature request: Ability to set priorityClassName #33

Open
M-Gregoire opened this issue Sep 21, 2022 · 1 comment
Open

Feature request: Ability to set priorityClassName #33

M-Gregoire opened this issue Sep 21, 2022 · 1 comment

Comments

@M-Gregoire
Copy link

Hello,

As far as I know, this Helm Chart doesn't offer this ability to set the priorityClassName to Frigate pods.

This might be useful as some pods in the cluster might need to have lower/higher priorities than Frigate.

If you are willing to implement this, I can make the PR.

@SlothCroissant
Copy link

I'd love this feature.

Use case:

  • Frigate pod deployed to Node A, with GPU and Coral applied as nodeselectors / resource limits.
  • Plex pod is deployed as well, I want to make sure frigate is never preempted by the Plex pod (as it also looks for GPU for hardware transcoding).

Since Frigate is "stuck" on a node due to hardware requirements from the Coral USB TPU, it doesn't have the luxury of just moving to another node. priorityClassName would mean that it doesn't have to, and it can actually boot other pods out as needed.

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 a pull request may close this issue.

2 participants