-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
Configuration #75
Configuration #75
Conversation
b986806
to
49b9446
Compare
I've removed the RFC label. This is hypothetically ready to merge. Critical feedback welcome. |
dask_kubernetes/core.py
Outdated
@@ -381,6 +392,8 @@ def scale_up(self, n, pods=None, **kwargs): | |||
-------- | |||
>>> cluster.scale_up(20) # ask for twenty workers | |||
""" | |||
if dask.config.get('kubernetes.count.max') is not None: | |||
n = min(n, dask.config.get('kubernetes.count.max')) |
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.
Would it be worth issuing a warning when n > kubernetes.count.max
? This may lead to surprising behavior when you can't scale beyond a certain threshold because of a parameter you didn't set.
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.
Looks good to me. Just one small comment.
We're updating configuration in dask/dask#3432
This affects downstream projects and makes it a bit easier for them to handle their own configuration files.
This PR shows how that configuration system might be used within dask-kubernetes. Review would be welcome. I recommend reading the documentation provided within dask/dask#3432 first.
cc @jacobtomlinson