We’re deploying JupyterHub with our own custom Authenticator in an extraConfig: section of the helm chart values which relies on a package not installed in the default image. We’ve been building our own image using the PIP_OVERRIDES to install the package but this is a maintenance headache.
I suppose I can maybe run some kind of package install in the extraConfig: section, but is there an official way of specifying that Hub should install extra packages at container startup before starting the Hub code? Or a JupyterHub pre-run section like the pods have?
My overall aim is to have all our site-specific config specified in the, well, config – and not have to maintain forks.
Read more here: Source link