-
### Proposed change
The kube spawner naming templates only support userid, username, and servername. When deploying multiple jupyterhubs in the same namespace (yes this is smth we would like to d…
-
### Bug description
To install custom configuration for a jupyterhub [helm release using terraform](https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release), the va…
-
### Proposed change
Use reflectors per each user namespace instead of shared reflectors across multiple namespaces for allowed `enable_user_namespaces`. Enabling `enable_user_namespaces` will c…
-
I searched for dependabot and pre-commit PRs to get them merged across the org and saw a few repo's with test failures in the CI system we should try to resolve.
## Links
- Look at [open pre-commi…
-
### Background by Erik
Z2JH introduced singleuser.extraFiles configuration, allowing Helm chart configuration values to be automatically translated as file content and mounted as a file on the disk…
-
## Update by @consideRatio
The environment variable should in order to follow common k8s security practices be mounted from a k8s Secret rather than set directly as a name/value pair in the k8s Pod…
-
**Describe the bug**
When deployed with jupyterhub, if I put the following line in jupyterhub config to enable the latest collaboration feature of jupyterlab
```
c.KubeSpawner.args = ['--coll…
-
## Update
To a large extent, this is addressed by #1923, see the checklist below.
---
It is a common practice to use the Helm _release name_ as a prefix to the k8s resource names. A Helm _rel…
-
### Context
Hubs using a profile list cannot quickly test a new image tag using the configurator. Instead, community reps need to request an update to the image and tag via a support ticket that we…
-
Thanks to efforts from me and @colliand, we've been able to get more resources from Development Seed for working with the NASA VEDA, GHG and ESDIS hubs. They're a very ideologically aligned organizati…