Jupyter Notebooks Overview

Menatic AI makes it easy to deploy personal JupyterLab notebook environments directly on your Kubernetes cluster.

What is a Notebook Instance?

Each notebook instance is a Kubernetes Deployment running JupyterLab. Instances are:

• Isolated — each user gets their own pod with independent storage
• Persistent — data is stored on a PersistentVolumeClaim that survives pod restarts
• Accessible — exposed via Traefik ingress at https://<domain>/jupyter/<name>/
• Secure — protected by a per-instance token with auto-login URL support

Notebook List

The Notebooks page shows all deployed notebook instances with:

Column	Description
Name	Notebook instance name (also the URL slug)
Status	Pod status: Running, Starting, Pending, Failed
Owner	User who owns this notebook
Usage	Real-time CPU (millicores) and memory (MB) consumption
Actions	Open, delete

Access Control

By default, admin users see all notebooks. Regular users with the jupyter:read permission see all notebooks; users with jupyter:read_own only see notebooks they own.

See Access & Permissions for details.

Resource Usage Column

The Usage column shows actual CPU and memory consumption fetched from metrics-server. This helps identify notebooks consuming excessive resources.

• Requires metrics-server to be installed
• Shows — if metrics are unavailable or the pod is not yet running
• Updates when the page is refreshed