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] Allow setting priorityclass of components #987

Open
ColonelBundy opened this issue Mar 22, 2023 · 0 comments
Open

[Feature] Allow setting priorityclass of components #987

ColonelBundy opened this issue Mar 22, 2023 · 0 comments

Comments

@ColonelBundy
Copy link

ColonelBundy commented Mar 22, 2023

Is this a BUG REPORT or FEATURE REQUEST?:
Feature

What happened:
Portworx pods were evicted due to it's lower priroityclass

What you expected to happen:
Being able to set the priorityclass of portworx components to prevent eviction.

Today all the components have no priorityclass set other than the default but the preemptionPolicy is set to PreemptLowerPriority which is good but it does not hinder eviction completely. I would very much like to be able to specify our own priorityclass and handle this on our own.

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

No branches or pull requests

1 participant