Kubernetes
The Kubernetes connector indexes deployment state into the local SQLite index and exposes a small read + HITL-gated write surface against whatever cluster your kubeconfig points at. The MCP server shells out to kubectl.
What’s indexed
Section titled “What’s indexed”- Service id:
kubernetes - Item types:
k8s_workload
Authenticate
Section titled “Authenticate”nimbus connector auth kubernetesStored in the Vault as kubernetes.kubeconfig (path) and optionally kubernetes.context. The kubeconfig path is exported into the connector spawn as KUBECONFIG; the optional context is passed via --context.
Read tools (no HITL)
Section titled “Read tools (no HITL)”| Tool | Purpose |
|---|---|
| k8s_deployment_list | List deployments in a namespace. |
| k8s_event_list | List events in a namespace. |
| k8s_pod_list | List pods in a namespace (default: default). |
Write tools (HITL-gated)
Section titled “Write tools (HITL-gated)”Every tool below requires interactive consent through the Gateway HITL gate before it executes.
| Tool | Purpose |
|---|---|
| k8s_deployment_scale | Scale a deployment. |
| k8s_pod_delete | Delete a pod. |
| k8s_rollout_restart | Restart a rollout (e.g. deployment). |
Platform notes
Section titled “Platform notes”- Requires the
kubectlCLI onPATHand a valid kubeconfig file. - The sync handler runs
kubectl get deployments -A -o jsononce per cycle. - The MCP server throws on startup if
KUBECONFIGis unset.