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

[Part 9 of #758] Preset: scheduling.nodeAffinity.matchNodePurpose #927

Merged
merged 4 commits into from
Sep 20, 2018

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Sep 11, 2018

To review


About

This preset makes pods of user | core kind either prefer require or ignore a scheduling on a node with a matching label for hub.jupyter.org/node-purpose: user | core.

@consideRatio
Copy link
Member Author

consideRatio commented Sep 11, 2018

This PR is very bugged... Apparently everything is up to date even though i try force push crap content. Also, the commits have a different order than they should have.

@consideRatio
Copy link
Member Author

Rewriting your Git commit history while performing rebases alters the space-time continuum, which means that commits may not be represented the way you expect them to in the GitHub

However, rest assured that nothing is broken when you see things outside of a chronological order!

All good then! Just make sure to ignore the commit order as viewed in GitHub.

Extra storage labels are now configurable through config.yaml and
`singleuser.storageExtraLabels`.
@consideRatio consideRatio force-pushed the 758-9-match-node-purpose branch from 413154b to 44c3c74 Compare September 19, 2018 12:09
<core|user> pods now get `tolerations` for the node taint
`hub.jupyter.org/dedicated=<user|core>:NoSchedule` that could optionally
be added to nodes or all nodes in a node group (aka. node pool).

Note that due to a bug with using the `gcloud` CLI, we also add the
toleration for the same taint where `/` is replaced with `_`.

In this commit, `singleuser.extraTolerations` are now also made
configurable allowing you to add your own custom tolerations to the
user pods.
These affinities allow for more fine grained control of where a pod will
schedule.
@consideRatio consideRatio force-pushed the 758-9-match-node-purpose branch from 44c3c74 to 972af40 Compare September 19, 2018 16:23
@minrk minrk merged commit 972af40 into jupyterhub:master Sep 20, 2018
Sieboldianus added a commit to Sieboldianus/zero-to-jupyterhub-k8s that referenced this pull request Aug 3, 2022
Originally `--enable-vmss`, changed to `--vm-set-type`, see [jupyterhub#927](927)

927: Azure/azure-cli-extensions#927 (comment)
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.

2 participants