-
Notifications
You must be signed in to change notification settings - Fork 216
Add cluster-critical priorityClass to machine-api #230
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 cluster-critical priorityClass to machine-api #230
Conversation
As of now, machine-api-operator doesn't have `system-node-critical` priority, the pods created for this deployment may get evicted by scheduler, if this priorityClass is not available. The rationale behind adding `system-node-critical` is we have nodeSelector to ensure that we are running on master nodes.
/retest |
/test integration |
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ingvagabund The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@ravisantoshgudimetla thanks :) |
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
…-logging Prepend machine.Name to all logging
As of now, machine-api-operator doesn't have
system-node-critical
priority, the pods created for this deployment may get evicted by scheduler, if this priorityClass is not available. The rationale behind addingsystem-node-critical
is we have nodeSelector to ensure that we are running on master nodes.