Releases: ml-tooling/ml-hub
Releases · ml-tooling/ml-hub
1.0.0
- simplified Kuberntes deployment - at least in our opinion ;) Modified Kubernetes artifacts/deployment to make it more consistent with our Docker-local deployment and JupyterHub in general.
- documentation updates with regards to Kubernetes deployment
- various bug fixes
- altered mount path of the dynamic whitelist file
0.1.10
- Add feature for dynamically whitelist usernames without the need to restart the hub container. See documentation for more information.
- Fix issue with logging in the Jupyterhub config
- Update base image ssh-proxy to version 0.1.11, which contains a bug fix in Kubernetes mode
0.1.9
0.1.8
0.1.7
- pre-install oauthenticator package to allow OAuth as Jupyterhub Authenticators (https://github.com/jupyterhub/oauthenticator)
- add normalization steps for user names. This is especially useful for oauthenticators, where the returned username can contain special characters such as spaces or commas which can lead to problems when routing requests. These added normalization steps can be overriden, if needed
- add update button to the hub home page, which users can use to update their default workspace server in case the hub container was updated with a new default workspace image
- [Docker-local only] add namespace support that allows having multiple MLHub containers with different names running on the same machine, as created artifacts such as other containers are named accordingly. The name for the hub container must be given via the environment variable
HUB_NAME
now and not via the docker--name
config anymore - [Docker-local only] add resource information to the "Create Named Server" page
0.1.6
- Fix issue with Jupyterhub config
base_url
, e.g.c.JupyterHub.base_url=/mlhub
works now. - HTTP is default now. SSL can be activated by setting the environment variable
SSL_ENABLED
to true, e.g.--env SSL_ENABLED=true
.- In the helm deployment, ssl can be activated by passing the environment variable to the proxy config
proxy.extraEnv.SSL_ENABLED=true
- The ssh feature is not supported in non-ssl mode.
- Like before, an unsigned ssl certificate is generated automatically if none is provided
- In the helm deployment, ssl can be activated by passing the environment variable to the proxy config
- In former versions, additional arguments could be passed to the chp-start command via container args. Now, this has to happen via the
ADDITIONAL_ARGUMENTS
environment variable, e.g.--env ADDITIONAL_ARGUMENTS="--ip=0.0.0.0 --api-ip=0.0.0.0"