-
Notifications
You must be signed in to change notification settings - Fork 813
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 11 of #758] Added scheduling.userPlaceholder
#929
[Part 11 of #758] Added scheduling.userPlaceholder
#929
Conversation
jupyterhub/templates/_helpers.tpl
Outdated
{{- /* | ||
A custom resource request. | ||
*/}} | ||
{{- define "jupyterhub.resources" -}} |
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.
I think this is a helpful rule of thumb: never make a helper that's only used once. This appears to only be used in one place. Even if you think it might be used elsewhere, the time to refactor is when you want to reuse it, not before.
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.
👍
It will be used in the user-dummy as well. Needing to make these helpers have made me cringe in general. I wonder if k-sonnet allows for better handling of combining dict values provided by the user than helm.
b1df768
to
208bcf1
Compare
jupyterhub/templates/_helpers.tpl
Outdated
|
||
{{- if and $r $l }} | ||
{{- println }} | ||
{{- end }} |
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.
It is valid, so lets not make the stuff more complicated, i think.
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.
This is now removed in the added commit to this PR.
Extra storage labels are now configurable through config.yaml and `singleuser.storageExtraLabels`.
208bcf1
to
57a6069
Compare
<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.
57a6069
to
79a6e28
Compare
Read about them in schema.yaml
79a6e28
to
ef102f8
Compare
To review
scheduling.userPlaceholder
optionAbout
Read about them in schema.yaml please, whats written here propagates to the configuration reference in the guide.