Jim Crist-Harif

Hmmm, from reading that issue it sounds like relying on a namespace-per-user wouldn't work for you? If that's the case, I'd be open to going down the route described here:...

> Please correct me if I'm wrong, but it seems like DG makes the assumption that the namespaces will be generated ahead of time. This will be difficult given that...

There's some tricky aspects to this, especially from the k8s side. I'm hoping to have time to work on it sometime soon (rather busy with work right now), but no...

Because the admin practices for each backend are different (e.g. on kubernetes admins would never write that file, they'd use helm), there hasn't been a need for documenting the `dask_gateway_config.py`...

Also note - most of the admin-side documentation is out of date since the rewrite. The process for everything non-kubernetes should remain the same, but the actual parameter field names...

We also document every configurable field here (although these are also out of date since the rewrite): https://gateway.dask.org/api-server.html

Your case is a bit odd because you're looking at extending dask-gateway, and we have no docs about that. Our docs are mostly focused at users and admin, with walkthroughs...

I'm going to keep this open to remind me to better document non-standard installs and configuration points.

Thanks for opening this issue. The resource-limit settings in dask gateway are actually per-cluster (e.g. max cores per cluster). Setting them as described in that doc set global defaults, but...

There's `idle_timeout` (https://gateway.dask.org/api-server.html#c.ClusterConfig.idle_timeout), a max time for the cluster to sit idle (unused) before it's culled, but there isn't a total max runtime for the cluster itself. That wouldn't be...