Capability · Network Isolation
Lock down agent egress with standard Kubernetes NetworkPolicy.
Zelkor blocks agent pods from calling the public internet, vector stores, sandbox workers, or external tools directly—allowing outbound traffic only to the AI gateway, the MCP gateway, and run state storage.
Why Default Kubernetes Networking Fails for Agents
By default, any Kubernetes pod can open outbound connections to the public internet and to internal services across namespaces. If an agent pod is compromised through a prompt or dependency, it can post stolen data to an external server or probe internal databases directly.
Default-Deny Agent Egress
Standard Kubernetes NetworkPolicy blocks agent pods from reaching the internet, Qdrant, sandbox workers, and external MCP servers directly. Outbound connections are limited to the AI gateway, MCP gateway, and checkpointer database.
Isolated Agent Namespaces
When namespace isolation is enabled, only pods in designated agent namespaces can connect to the run-state database, blocking lateral movement from unrelated workloads on the cluster.
No Public Routes to Internal Services
Only the authenticated Envoy front door is exposed outside the cluster. Internal services—including the MCP gateway, NeMo Guardrails, databases, and sandbox workers—never get public routes.
Works With Your Ingress and Quotas
Deploy Envoy as a standalone load balancer, behind your existing ingress controller, or attached to a shared cluster gateway. Every container includes CPU and memory requests and limits to pass strict namespace quotas.
How Teams Use It
platform:
isolation:
agentNamespaces: true
security:
networkPolicies:
enabled: true
gateway:
hosts:
agents: "agents.example.com"
langfuse: "langfuse.example.com"Lock down agent network traffic using standard Kubernetes controls on any CNI.