Multi-cluster

Laptop-local multi-context: aliases, read fan-out, per-context mutate safety, fleet optimize. Not a hosted Lens/fleet SaaS — kubeconfig never leaves your machine.

kprompt’s multi-cluster story is laptop-local: aliases and explicit fan-out over your kubeconfig contexts. Credentials stay on the device. The optional Team control plane may later store metadata only (display name, alias, which enrolled CLI can reach a cluster) — never kubeconfig upload.

Inventory & aliases

kprompt contexts
kprompt contexts --check
kprompt config alias set prod gke_myproj_us-central1_prod
kprompt --context prod "list deployments"
kprompt config set require_alias_match true

Read fan-out

Opt-in only — never “all contexts” by default. Supported: get/list, explain, logs, describe, optimize. JSON kind MultiContextResult includes per-context steps and cluster_context; optimize adds fleetSummary.

kprompt --contexts staging,prod "list deployments"
kprompt "list pods across staging and prod"
kprompt --contexts staging,prod "optimize my cluster"

Mutate safety

  • Interactive: confirm each context separately
  • Plain --approve across multiple contexts is refused
  • --approve-each-context is the explicit multi-apply escape hatch
kprompt --contexts staging,prod "scale api to 3"
kprompt --contexts staging,prod --approve-each-context "scale api to 3"

What this is not

  • Not uploading kubeconfigs to api.kprompt.ai or app.kprompt.ai
  • Not a hosted live multi-cluster browser (Lens/Headlamp clone)
  • Not silent --approve across every context
  • Not an always-on in-cluster multi-cluster agent
  • Not a replacement for kprompt-dash’s single-cluster localhost inventory