zero-to-jupyterhub-k8s
zero-to-jupyterhub-k8s copied to clipboard
Helm Chart & Documentation for deploying JupyterHub on Kubernetes
Hi, I was requested by a client to label all k8s objects of the Jupyterhub helm chart with additional, team specific informations. Therefore I added a helper function called **jupyterhub.determinedLabels**...
## Update Security vulnerabilities reported in `debian` based images doesn't seem less safe than `ubuntu`. They both have security overviews, and the key difference is how security scanners like `trivy`...
User may set up `kubespawner.proxy.KubeIngressProxy` which allows to use builtin k8s Ingress to create routes for hub, user notebooks and services. But this helm chart will always create proxy pod...
## Wishes before we cut 4.0.0-beta.1 - [ ] KubeSpawner release https://github.com/jupyterhub/kubespawner/issues/850 - [x] LDAPAuthenticator 2 release - https://github.com/jupyterhub/ldapauthenticator/issues/220 - [x] JupyterHub 5.2.0 release? https://github.com/jupyterhub/jupyterhub/issues/4917 - [x] Oauthenticator 17 release...
A rebuild of `quay.io/jupyterhub/k8s-singleuser-sample` has been found to influence the detected vulnerabilities! This PR will trigger a rebuild because it has updated a comment in the Dockerfile. ## About This...
A rebuild of `quay.io/jupyterhub/k8s-hub` has been found to influence the detected vulnerabilities! This PR will trigger a rebuild because it has updated a comment in the Dockerfile. ## About This...
A rebuild of `quay.io/jupyterhub/k8s-secret-sync` has been found to influence the detected vulnerabilities! This PR will trigger a rebuild because it has updated a comment in the Dockerfile. ## About This...
Firstly, I apologize for the delay in submitting this PR. Configuring the local build of the documentation proved to be a bit challenging, requiring additional time to ensure proper setup....
Hello JupyterHub team, I've been exploring the current documentation and setup processes for JupyterHub on Kubernetes, primarily managed through Helm. This setup works well for basic deployments, but I've noticed...