Releases: nebari-dev/nebari
Releases · nebari-dev/nebari
v0.3.1
Feature changes an enhancements
- added gitlab support for CI
ci_cd
field is now optional- AWS provider now respects the region set
- More robust errors messages in cli around project name and namespace
git init
default branch is nowmain
- branch for CI/CD is now configurable
Bug fixes
- typo in
authenticator_class
for custom authentication
v0.3.0
Feature changes and enhancements
- Added support for self-signed certificate/secret keys via Kubernetes secrets.
- JupyterHub-SSH (
ssh
andsftp
integration) accessible on port8022
and8023
, respectively. - VSCode(code-server) is now provided in default image and integrated with JupyterLab.
- Dask Gateway is now locally accessible.
- Moved fully towards Traefik as a load balancer, with tight integration with Dask-Gateway (to replace nginx).
- Added ability to specify node selector label for general, user, and worker.
- Included the ability to specify
kube_context
for local deployments; (If not specified, it will usedefault
). - Adopted a strict schema validation for the configuration file (
qhub-config.yaml
). - Terraform binary is now auto-installed and its version managed automatically by QHub (no more Terraform manual install).
- Removed the need for the
qhub render
command for end-users, now the deploy stage will auto-render by default. - Support for namespaces with QHub deployments on Kubernetes clusters.
- Full JupyterHub theming that allows users to tailor their own QHub UI - including colors, on the config file.
- JupyterHub Docker image is now independent of zero-to-jupyterhub.
- JupyterLab 3 is now the default user Docker image.
- Implemented the option to locally deploy QHub, allowing for local testing of clusters.
- Removed the requirement for DNS and added password-based authentication. OAuth requirements, no more.
- CI now tests local deployment on each commit/PR.
- QHub Terraform modules are now pinned to specific git branch via
terraform_modules.repository
andterraform_modules.ref
. - Adds support for Microsoft Azure Cloud provider.
- Revamped the documentation and added a tutorial on Dask Gateway usage
- Added integration with CDS Dashboards. Support for any dashboard that uses HTTPS but current implementation serves Voila, Streamlit, Bokeh, PlotlyDash, and Shiny out-of-the-box.
Breaking changes
- Terraform version is now pinned to a specific version
domain
attributed inqhub-config.yaml
is now the URL for the cluster
v.0.2.3: Merge pull request #292 from Quansight/release-023
Release v0.2.3
Release - v.0.2.2
- Added prefect integration
Release - v.0.2.1
- Define supported terraform versions
- Add CNAME support for AWS
- Change
master
branch name tomain
Release - v.0.2.0
Release 0.2.0 🎉
Features changes and enhancements
- Added conda prerequisites for GUI packages.
- Added
qhub destroy
functionality that tears down the QHub deployment. - Changed the default repository name from
master
tomain
. - Added error message when Terraform parsing fails.
- Added templates for GitHub issues.
Bug fixes
qhub deploy -c qhub-config.yaml
no longer prompts unsuported argument forload_config_file
.- Minor changes on the Step-by-Step walkthrough on the docs.
- Revamp of README.md to make it concise and highlight QHub OnPrem.
Breaking changes
- Removed registry for DigitalOcean.
Thank you for your contribution!
Brian Larsen, Rajat Goyal, Prasun Anand and Rich Signell and Josef Kellndorfer for the inspiring discussions.
Stability updates
Added requirement of terraform_version
in qhub-config.yaml
Stability changes
v0.1.20: Merge pull request #179 from Quansight/update_stepxstep
Update stepxstep
v0.1.19: Merge pull request #111 from Quansight/release-0-1-19
Bump version to 0.1.19
Minor bug fix
Fixes bug where qhub render
creates an incorrectly formatted terraform file