K8s Dashboard · Showcase

Multi-cluster setup

Every cluster gets its own agent + tunnel + dashboard entry. Switch in the header, or aggregate on Pro.

Adding clusters

Each cluster is a separate Helm install with its own registration token. Mint one token per cluster from Settings → API Keys.

# Cluster A
helm install klstr-agent https://app.klstr.dev/install/klstr-agent-chart.tgz \
  --set agent.registrationToken="k8s_reg_XXXX_A" \
  --namespace klstr-agent \
  --create-namespace

# Cluster B
helm install klstr-agent https://app.klstr.dev/install/klstr-agent-chart.tgz \
  --set agent.registrationToken="k8s_reg_XXXX_B" \
  --namespace klstr-agent \
  --create-namespace

Each cluster gets:

  • Its own Cloudflare tunnel hostname
  • Isolated graph + compute (no cross-cluster pollination)
  • Its own row in Clusters with independent health badge

Switch vs aggregate

The dashboard header has a cluster switcher by default — click, pick a cluster, every view rescopes. Works on every tier.

Multi-cluster aggregated view (Pro+) shows you:

  • Pods / Services / Nodes across selected clusters in one table
  • Cross-cluster events timeline
  • Per-cluster health scoreboard
  • Side-by-side comparison of two clusters (diff mode)

Toggle it from the cluster switcher → Select multiple.

Topology queries (blast-radius, correlation) stay cluster-scoped — clusters are isolation boundaries by design. Use multi-cluster for fleet-wide visibility.

Name collisions

klstr namespaces everything by cluster ID, not cluster name, so you can have five clusters all called default or production without collision. The display name you set in the registration form is what shows in the switcher.

Cluster cap by plan

  • Free — 3 clusters · 10 nodes each
  • Pro — up to 25 clusters at $99/cluster/month (or $990/cluster/year, save 17 %). Each cluster includes 50 nodes; additional nodes are metered at $2/node/month.
  • Enterprise — unlimited clusters and nodes, contract pricing from $25k/year.

Hit the cap on Free? The dashboard prompts an upgrade when you try to register the 4th cluster. See billing for the detailed plan comparison or /pricing for the full matrix.

Removing a cluster

  1. In the dashboard, Clusters → ⋯ → Delete
  2. klstr tears down the Cloudflare tunnel + Access service token
  3. helm uninstall klstr-agent --namespace klstr-agent from the cluster itself

The cluster's graph data is discarded (Durable Object deleted), the row in Clusters is cleared, and any open dashboards auto-refresh.