Built a Kubernetes CLI where the LLM is strictly sandboxed — parses intent only, never touches the cluster
Hey ,
Most NL Kubernetes tools pipe your prompt straight to an LLM and let it drive execution. KubeNexus doesn't work that way.
The LLM (gemma4:e2b via Ollama) is parser-only. It converts your plain English into a structured JSON intent object and that's it. A separate engine layer handles all kubectl execution. The model never sees cluster data, never generates commands directly, never has network access.
kubenxs run "deploy myapp with nginx image, 3 replicas"
kubenxs run "scale myapp to 5 replicas"
kubenxs run "rollback myapp"
kubenxs history
On top of that:
- Secret interception before the prompt ever reaches the LLM (AWS keys, bearer tokens, kubeconfig paths, base64 blobs, private key headers)
- Destructive actions require a 5-second TTY confirmation — no accidental deletes
- Every action logged with UUID + SHA256 for tamper detection
- StatefulSet + headless service auto-generated for DB/queue workloads
- Drift check before every rollback
- Runs fully local — no cloud APIs, no data leaving your machine
v0.1.0, early alpha, fully functional.
pip install kubenxs
GitHub: https://github.com/ManiacBeast20/KubeNexus-v2
Brutal feedback welcome — what would actually make this useful in your workflow?