The same OpenAI call going to NAI on CPU and to a GB10 GPU just by changing the model, +40% tokens/s on CPU with one variable, vLLM metrics in the NKP Grafana, the Agentic Gateway with a unified endpoint, token-based rate limiting and MCP, and NAI protected with Velero and NDK, with the best practices and the real numbers.
A dedicated NKP 2.19 cluster, the seven catalog dependencies, NAI 2.8.1 with a certificate from the internal CA, the license applied on day one, a validated model and a custom one from Hugging Face, and the first endpoint answering on CPU, with the prerequisites that make the install go smoothly and the real numbers.
The RWX storage NAI requires, from scratch: Nutanix Files 5.4 deployed from Prism Central in 27 minutes, NFS v3 and v4, the NKP CSI in Prism Central mode talking to the Files v4 API, and a ReadWriteMany volume ready in 6 seconds, with two pods on different nodes writing to the same file.
Before clicking Enable: what Nutanix Enterprise AI is, how it is licensed (vCPU or GPU memory, with a 2-day trial), what the 2.8.1 User Guide requires, how much the control plane consumes, what changes without a GPU and what the two Nutanix Validated Designs recommend. And the lab's decision: a dedicated cluster, with the memory math done first.