Multi-Cluster

Work across several kubeconfig contexts without losing which cluster each resource came from.

Overview

Krust lets you toggle multiple Kubernetes contexts simultaneously and view resources from all selected clusters in a unified interface.

This matters during real operations: staging and production often need to be compared side by side, regional clusters can drift, and incidents frequently start with the question "is this only one cluster or everywhere?"

Context Management

Click a context name in the sidebar to switch to it
Toggle multiple contexts for side-by-side view
Each context gets its own API client and watchers

Each active context keeps its own Kubernetes client and watcher set. That keeps updates scoped to the cluster they came from while still presenting the result in one operational view.

Side-by-Side Views

Resources from all selected clusters appear in the same table. A cluster badge on each row identifies the source cluster.

Use this when checking whether a Deployment exists in both clusters, whether image versions match, or whether one region is failing while another is healthy.

Synchronized Filtering

Namespace filtering applies across all active contexts, keeping the view consistent.

Table filters also stay useful in multi-cluster mode because cluster identity is visible on each row. You can narrow by namespace, status, workload name, or any structured filter while keeping the cluster badge in view.

Common Workflows

Staging vs production checks — verify image tags, replica counts, and rollout status before or after a deploy.
Regional incident triage — compare pods, services, and events across clusters to see whether a failure is local or global.
Shared config audits — inspect ConfigMaps, Secrets metadata, and Helm releases across contexts without changing tools.

Cross-Cluster Diff Pro

Compare resources between different contexts/clusters:

Select a source resource and a target resource from different clusters
See a unified diff with colored additions and deletions

Note: same-context resource diff remains free. The cross-context workflow is Pro-gated.

See Pro Diff Features Read YAML Diff Docs

kubeconfig Auto-Watch

Krust detects changes to your kubeconfig file and auto-reloads contexts without requiring a restart.

This is useful when your cloud CLI refreshes credentials, a new context is added, or a context is renamed outside Krust. If a cluster disappears or credentials expire, Krust keeps the failure scoped to that context instead of blocking unrelated clusters.