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

Add support to mention priorityClassName for Fission components #2254

Merged
merged 1 commit into from Nov 8, 2021

Conversation

sanketsudake
Copy link
Member

In Fission CI as well in couple of scenarios, noticed Fission pods
getting preempted when Function pods are getting created. As both
Fission components and function pods have same priority class
fission component pods might get preempted. It to be recommended to
set higher priority class for components such as Fission router, executor,
controller so that Fission functioning doesnt get disrupted.
Most of Fission components work fine with restart except executor. So
user should set priorityClass for Fission executor.

Signed-off-by: Sanket Sudake sanketsudake@gmail.com

In Fission CI as well in couple of scenarios, noticed Fission pods
getting preempted when Function pods are getting created. As both
Fission components and function pods have same priority class
fission component pods might get preempted. It to be recommended to
set higher priority class for components such as Fission router, executor,
controller so that Fission functioning doesnt get disrupted.
Most of Fission components work fine with restart except executor. So
user should set priorityClass for Fission executor.

Signed-off-by: Sanket Sudake <sanketsudake@gmail.com>
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

1 participant