-
Notifications
You must be signed in to change notification settings - Fork 970
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
Don't depend on ready condition of nodes instead of taints in session #3756
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Signed-off-by: Monokaix <[email protected]>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hwdef 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 |
/ok-to-test |
Some cni plugin need deployed first then the node can get ready,so we should not filter not ready node in scheduler,instead the node will be tainted by kube controller when node not ready,and pod will not be scheduled by default,also pod can set tolerations to get scheduled.
xref: https://github.com/kubernetes/design-proposals-archive/blob/main/scheduling/taint-node-by-condition.md
previous pr:#507