Skip to main content
The UI installs the same way as the operator, from the same private registry — the access token you already have works for both. If you don’t have one, request it from the Tensormesh team.
Install the Tensormesh Operator and at least one LMCacheEngine first — the UI is a read-only dashboard over your engines. It installs fine on an empty cluster but shows “No LMCacheEngines found” until engines exist.

​
Prerequisites

  • Helm 3.8 or newer (helm version)
  • A Kubernetes 1.28+ cluster with the Tensormesh Operator installed, plus at least one LMCacheEngine
  • Prometheus running in the cluster, with the operator’s metrics flowing into it (observability.enabled=true on the operator chart — see Operator Observability). This powers every trend chart.
  • The NVIDIA DCGM exporter, if you run GPUs — standard on GPU clusters (it ships with the NVIDIA GPU Operator, and isn’t part of Tensormesh). It drives the per-GPU utilization, memory, and hardware-fault cards.
  • An access token from the Tensormesh team — the operator’s token works
  • The GHCR image pull secret you created for the operator

​
Versions

Use the newest chart version below wherever a command says <version>. Like the operator’s compatibility matrix, each row is a matched set — run the UI chart against the operator versions listed with it.

​
Install

1

Log in to the Registry (One Time)

If you already logged in to install the operator, skip this step.
2

Write a Values File

my-values.yaml
The UI picks up cluster access automatically once it’s running inside the cluster — you never set a kube API URL or token. See Configuration for how each value maps to what you see, plus multiple clusters.
3

Install

Replace <version> with the newest chart version from the table above — never latest, so you always know exactly what’s running.

​
Verify

The bundled test confirms the UI is up and serving. If anything looks off once you open the dashboard, see Troubleshooting & FAQ.

​
Open the Dashboard

The install doesn’t expose the UI outside the cluster. To open it, port-forward the service:
For shared team access, enable the ingress (ingress.enabled=true with your own hosts and TLS).
The UI has no built-in login — if you expose it beyond port-forward, put SSO in front at the ingress. See Access & Security.

​
What Gets Installed

A single dashboard pod and a service — nothing on your GPU nodes. Its cluster access is strictly read-only: it can look at engines, pods, and metrics, and cannot modify anything.

​
Upgrade

Re-run the install with a new --version (same values file):
Roll back if needed:

​
Uninstall

The UI keeps no cluster state, so nothing is left behind.

​
Next Steps

Configuration

Connect metric history, GPU telemetry, and multiple clusters.

Monitoring Your Fleet

Triage what needs attention, drill into nodes and GPUs, and track cache and performance trends.