Quick Start
Operator-managed install (default)
Section titled “Operator-managed install (default)”On a NIC-managed cluster, the Nebari Operator
and ArgoCD install this chart for you — you don’t run helm commands
yourself. The values most deployers adjust:
keycloak: hostname: keycloak.example.com # only field required for a zero-config deploy
nebariapp: enabled: true # register with the Nebari Operator via the NebariApp CRD hostname: "" # derived as hub.<base-domain-of-keycloak.hostname> when empty
sharedStorage: enabled: true storageClass: longhorn # set on clusters with a native RWX StorageClassInstall from the Helm repository
Section titled “Install from the Helm repository”helm repo add nebari https://raw.githubusercontent.com/nebari-dev/helm-repository/gh-pages/helm repo updatehelm install data-science-pack nebari/nebari-data-science-packAlso available as an OCI artifact (no helm repo add needed):
helm install data-science-pack oci://quay.io/nebari/charts/nebari-data-science-pack --version <version>Install from source
Section titled “Install from source”git clone https://github.com/nebari-dev/data-science-pack.gitcd data-science-packhelm dependency updatehelm install data-science-pack . --namespace defaultAccess JupyterHub
Section titled “Access JupyterHub”kubectl port-forward svc/proxy-public 8000:80Open http://localhost:8000 — with the dummy authenticator, any username/password works.
Local development
Section titled “Local development”Prerequisites: Docker, ctlptl, Tilt.
# Start local k3d cluster + Tilt dev loopmake up
# Tilt UI: http://localhost:10350# JupyterHub: http://localhost:8000
# Tear downmake down