-
Notifications
You must be signed in to change notification settings - Fork 97
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
Allow jupyterhub.overrides in qhub-config.yaml #930
Conversation
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.
LGTM, I will test this and see how that goes, thanks @danlester
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 a great addition. @danlester could you add this to the docs?
Added docs, but actually I still want to test the upgraded helm chart more first. |
The latest Helm charts (0.10.0 onwards, including 1.2.0) have a strict networkPolicy as default. This prevented access from hub to Keycloak, and also from singleuser pods to Dask etc. It only appeared to affect Digital Ocean, not Google Cloud. This may be due to a different network system being in use. I have disabled the networkPolicy in hub and singleuser now. |
Also closes #926 |
Changes:
Closes #814
Types of changes
What types of changes does your code introduce?
Put an
x
in the boxes that applyTesting
Requires testing
In case you checked yes, did you write tests?