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 11 of #758] Added scheduling.userPlaceholder #929

Merged
merged 7 commits into from
Sep 20, 2018

Conversation

consideRatio
Copy link
Member

@consideRatio consideRatio commented Sep 11, 2018

To review


About

Read about them in schema.yaml please, whats written here propagates to the configuration reference in the guide.

{{- /*
A custom resource request.
*/}}
{{- define "jupyterhub.resources" -}}
Copy link
Member

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.

Copy link
Member Author

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.

@consideRatio consideRatio force-pushed the 758-11-user-placeholder branch 2 times, most recently from b1df768 to 208bcf1 Compare September 16, 2018 11:46

{{- if and $r $l }}
{{- println }}
{{- end }}
Copy link
Member Author

@consideRatio consideRatio Sep 17, 2018

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.

Copy link
Member Author

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`.
@consideRatio consideRatio force-pushed the 758-11-user-placeholder branch from 208bcf1 to 57a6069 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-11-user-placeholder branch from 57a6069 to 79a6e28 Compare September 19, 2018 16:29
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