Manage Kubernetes
Import a kubeconfig, inspect your clusters in plain language, and run kubectl through the copilot — with changes gated behind confirmation.
emma can work with your Kubernetes clusters the same way it works with the rest of your infrastructure:
import a kubeconfig, ask about workloads in plain language, and run kubectl through the copilot.
Read-only queries run freely; anything that changes the cluster waits for your confirmation.
Before you start you need a cluster and its kubeconfig. If your cluster is already managed by emma, skip to step 2.
1. Import a kubeconfig
Add your cluster so the copilot can reach it.
Try this — Import this kubeconfig (then paste or attach it)
emma registers the cluster and it becomes available to the copilot and the diagram.
A kubeconfig grants access to your cluster — import only configs you trust, scoped to the access you intend to give.
2. Inspect your workloads
Ask about the cluster in plain language — no need to remember exact kubectl syntax.
Try this — Show me the pods in the payments namespace
emma runs the read-only query and summarizes the result, and you can drill in from there
(which of those have restarted recently?).
3. Run kubectl commands
You can also have emma run kubectl for you. Read commands run immediately; anything that mutates the
cluster — scaling, deleting, applying — is turned into a change you must confirm.
scale the api deployment to 5 replicas).Cluster-changing commands are gated like any other infrastructure change — see Safety & confirmations.
What's next
- Set up alerts — get notified about cluster health
- The diagram — see clusters and workloads on the canvas
- Export to infrastructure-as-code — codify cluster resources
Last updated on 17 Jul 2026