-
Notifications
You must be signed in to change notification settings - Fork 798
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
JupyterHub 3+ would block internal DNS by default? #3398
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Z2JH 2 contained some breaking changes regarding the network policy rules, have a look at Note that Z2JH 2 is still very old and unsupported, the most recent release is 3.3.7. |
Hi there @linlol 👋! I closed this issue because it was labelled as a support question. Please help us organize discussion by posting this on the https://discourse.jupyter.org/ forum. If it's your first time posting Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other. Thanks you for being an active member of our community! ❤️ |
Thanks @manics, I would check my helm configuration! |
btw @manics Is there any migration guide for z Or the change is generally backward compatible except db change |
There isn't a migration guide besides the changelog listing what should be considered for z2jh 2 -> 3 |
I am using JupyterHub with https://github.com/jupyterhub/zero-to-jupyterhub-k8s and I found issue during upgrade.
Currently I am using z2jh 1.2.0 with JupyterHub 1.5.0, and I am planning to upgrade to z2jh 2.0.0 and hub 3.0.0
looks like after upgrade, I can no longer send internal request thru Service within the same namespace like curl https://${SVC_NAME}/${ENDPOINTS}
Seems like the connection between lab and hub is great, but for other services which is not managed by z2jh helm, JupyterLab cannot access them via internal DNS
Is it something disabled due to the rbac feature?
The text was updated successfully, but these errors were encountered: