zero-to-jupyterhub-k8s
zero-to-jupyterhub-k8s copied to clipboard
Helm Chart & Documentation for deploying JupyterHub on Kubernetes
## Current state In 3.3.2 we now pin to `alpine:3.18` in our network-tools image, its used by an init container for user pods to block traffic to the cloud metadata...
This issue is linked from https://github.com/jupyterhub/jupyter-server-proxy/security/advisories/GHSA-w3vc-fx9p-wp4v from within the configuration below, meant to help patch the vulnerability within a user server before the jupyter server starts. This issue is meant...
[`singleuser.cloudMetadata.blockWithIptables`](https://z2jh.jupyter.org/en/latest/resources/reference.html#schema-singleuser-cloudmetadata-blockwithiptables) works by [adding an init container](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/cd8a7245618693c9f72a4633530f9799614a451d/jupyterhub/files/hub/jupyterhub_config.py#L424-L454) to block access to the cloud metadata server. While this hasn't happened often to my knowledge, in #3355 we had a k8s cluster...
A new jupyterhub version has been detected, version `5.0.0b2`.
### Bug description I'm deploying JupyterHub on GKE. I'd like there to be a separation between the default pool and a user pool, so I can use gvisor for [container...
A new kube-scheduler image version has been detected, version ``.
This pull request introduces the option to define a ServiceAccount in DaemonSets used in the prepuller. Closes https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/3442
### Bug description Even though `prepuller.hook.serviceaccount` is properly configured, these changes aren't applied in the pods ### How to reproduce 1. Configure `prepuller.hook.serviceaccount` with a service account 2. Apply the...
### Bug description We are using z2jh helm chart on our Kubernetes cluster, we upgraded the chart to the latest version (3.3.7) from 3.1.0. When the upgrade was finished; we...
### Bug description ### How to reproduce 1)Created a user testing 2)Was able to successfully login using testing username 3)Edited the user name to testing1 4)Says incorrect username and password...