Skip to main content

Multi-Cluster Windows

Open side-by-side browser windows against different clusters, contexts, or namespaces.

Opening a new window​

Dots menu → New Window.

The new window starts on the same kubeconfig/context as the current one but is fully independent — changing kubeconfig in one doesn't affect the others.

What's independent per window​

  • Kubeconfig
  • Context
  • Namespace
  • Resource kind
  • Filters (search, column filters)
  • Sort order
  • Row selection
  • Graph / Table mode

Each window runs its own:

  • Watch API stream.
  • Metrics polling.
  • WebSocket connections for ArgoCD / Helm health.

Window titles​

Titles show the kubeconfig (and context when the kubeconfig has multiple contexts):

Cluster - prod.kubeconfig
Cluster - dev.kubeconfig (ctx-dev)

Child windows spawn on the parent​

When you open Info / Shell / Logs / PortForward / Diff from a cluster window, the child window appears centered on the parent. Keeps related windows grouped visually across monitors.

Cross-window Diff​

The killer feature for cross-cluster comparisons:

  1. Open two cluster windows — e.g. staging and prod.
  2. In window A, right-click a resource → Diff.
  3. In window B, right-click the resource you want to compare → Diff.
  4. A diff viewport opens showing both side-by-side.

The diff viewport labels each pane with the kubeconfig/context, so you can see at a glance which is which:

my-pod (staging-kubeconfig/ctx-stage)    vs    my-pod (prod.kubeconfig/ctx-prod)

Works across any two resources, even different kinds (though the diff tends to be messy in that case).

Context menu parity​

Every action available in the main window is available in every cluster window: Info, Edit, Shell, Logs, Stats, Port Forward, Restart, Scale, Delete, Helm ops, ArgoCD ops, etc.

Toolbar in cluster windows​

Cluster windows have the same toolbar + Dots menu. A few items are hidden until resources finish loading:

  • Create (hidden until API resources are discovered).
  • Columns (hidden until a kind is selected and loaded).

Tips​

  • Compare configs across environments — open staging and prod side-by-side, navigate to the same Deployment in both, Diff. Fast sanity-check before cutting a release.
  • Keep production in a separate window — visually distinct windows reduce the risk of accidental Delete on the wrong cluster. Consider using a different theme per window to further differentiate.
  • Close cluster windows to free resources — each runs its own watches. A half-dozen windows on large clusters can add up.
  • Copy the context/kubeconfig label from diff headers when filing issues — makes the bug report self-describing.