I’m enabling auth state persistence in JupyterHub by following @minrk suggestion here.
I generate and set auth.state.cryptoKey and everything works fine. But I’m wondering if there’s a way to tell JupyterHub to generate it’s own random cryptoKey. That way JupyterHub’s auth persistence is “self contained”.
I would absolutely love to do this. However, there are challenges with the “generate secrets by default” pattern with helm (it’s not supported at all, but there are workarounds). We have an issue about this: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/1017