NVIDIAAnurag KuppalaTutorial
Deploy a Production-Ready NVIDIA AI-Q Blueprint on Oracle Cloud Infrastructure
Summary
The NVIDIA AI-Q Blueprint operates as an open-source reference architecture for long-horizon agents built upon LangChain Deep Agents and the NVIDIA NeMo Agent Toolkit. Deploying this multi-agent system on Oracle Cloud Infrastructure requires coordinating foundational cloud infrastructure with containerized application workloads across Kubernetes. The deployment methodology utilizes Terraform to provision network isolation, an enhanced OKE cluster, a flexible public load balancer, and an AES-256 encrypted OCI Vault. Helm manages the application layer on Kubernetes by pulling official images from the NGC registry to run a FastAPI agent backend, a Next.js web frontend, and PostgreSQL. This configuration establishes an extensible routing architecture where user queries route automatically between shallow search agents and deep planning sub-agents while maintaining clean infrastructure teardown commands.
Context
Developers and platform engineers need a reproducible method to deploy and run the NVIDIA AI-Q multi-agent blueprint in a production-ready cloud environment rather than locally on a laptop.
Approach / What changed
The system uses Terraform to provision OCI resources—including a VCN, an OKE cluster, a flexible load balancer on port 80 forwarding to NodePort 30080, and OCI Vault for credential storage. Helm installs the AI-Q 2.0 container workloads on OKE, configuring a FastAPI agent backend, a Next.js frontend, and an in-cluster PostgreSQL instance backed by dynamic OCI Block Volume storage.
Takeaways
NVIDIA AI-Q routes queries through an intent router either to a fast Shallow Research Agent or to a Deep Agent combining planning and research sub-agents with sandboxed tools.
The NGC API key serves a dual role in deployment, acting as the NVIDIA inference authentication key and as the image pull credential for the nvcr.io container registry.
While Terraform stores API keys in OCI Vault for disaster recovery, active Kubernetes pods read credentials directly from Kubernetes secrets, requiring pod rollouts upon secret rotation.
Source and freshness
- Source
- developer.nvidia.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.