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

Handle the 'NoSchedule' taint on nodes properly #458

Merged
merged 1 commit into from
Jan 30, 2018

Conversation

yuvipanda
Copy link
Collaborator

This is usually used to prevent pods from scheduling on a node
without explicit tolerations. The defaults for many cluster management
setups (such as https://github.com/Azure/acs-engine and I think
many amazon setups) use this to prevent master from being scheduled,
so we should respect this.

Fixes #454

This is usually used to prevent pods from scheduling on a node
without explicit tolerations. The defaults for many cluster management
setups (such as https://github.com/Azure/acs-engine and I think
many amazon setups) use this to prevent master from being scheduled,
so we should respect this.
@yuvipanda
Copy link
Collaborator Author

I'm pretty sure we need this for 0.6

Copy link
Collaborator

@willingc willingc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yuvipanda LGTM

}
}

return !node.Spec.Unschedulable
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotta love the double negatives.

@yuvipanda yuvipanda requested a review from minrk January 30, 2018 05:26
@minrk minrk merged commit dcb92ba into jupyterhub:master Jan 30, 2018
yuvipanda added a commit to yuvipanda/datahub-old-fork that referenced this pull request Jan 30, 2018
Should bring in version of prepuller with
jupyterhub/zero-to-jupyterhub-k8s#458 fixed.
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.

3 participants