Enable specific hub features

There are several extra features and services that can be enabled on the 2i2c JupyterHubs. These add extra functionality, connect with cloud services, etc. See the sections below for more details.

Layers

Cloud Layer

• 1.1. New Kubernetes cluster on GCP or Azure
• 1.2. New Kubernetes cluster on AWS
• 2. Dedicated nodepool on a shared cluster (recommended for events)

Access Layer

• 1.1. Authenticate using CILogonOAuthenticator
• 1.2. Authenticate using GitHubOAuthenticator
• 1.3. Authenticate using TmpAuthenticator for an Ephemeral hub
• 2. Anonymize usernames

Community Customization Layer

• 1. Community specific hub domain
• 2. Configure the hub login page

3. Customizations of hub pages

Data Layer

• 1. Shared data directories
• 2. Object storage buckets (persistent/scratch)
• 2.1. Cloud Permissions
• 3. Setup a database server per user
• 4. Setup a shared database for all users on the hub

Integrations Layer

• 1. Allow users to push to GitHub from the Hub (gh-scoped-creds)
• 2. Enable `nbgitpuller` for private repos (git-credential-helper)
• 3. Authenticated static websites
• 4. (default enabled) Configurator
• 5. (dedicated clusters only) Grafana

Performance Layer

• 1. GPU
• 2. Cull resources (jupyterhub-idle-culler)

3. Dask

Elastic scaffolding Layer

1. ProfileLists

• Hardware Profiles

• User Image Selectors

• Node Sharing

• 2. Allow users to setup custom, free-form user profile choices

User image

• Enable user image features
• Use Rocker based R images

Other possible layers, but not stabilized yet

• Knowledge sharing Layer

• Support Layer

• Applications Layer