AI Pilot capability matrix

Audience: Platform engineers, AI governance owners
Time: ~10 min read

This matrix maps common operator goals to native AI Gateway CRDs (the Kubernetes profiles AI Pilot targets), ext_proc / AIGatewayFilter, OPA (PBAC), PIP data, and Control Plane UI paths. Use it to avoid duplicating gateway features in custom PEP code.

GoalAI Gateway CRDsext_proc / AIGatewayFilterOPA + RegoPIPControl Plane UI
Multi-provider routing & fallbacksAIGatewayRoute, AIServiceBackend, BackendSecurityPolicyFilter chain hooks onlyAllow/deny overlaysAttribute factsSettings → AI Pilot → Routing; /pilot Routing tab
Token-aware rate limitsBackendTrafficPolicyCost obligations (audit)Usage snapshotsRate limits in routing bundle
Circuit breaker / retries / hedgingBackendTrafficPolicySettings → AI Pilot → Resilience
MCP broker / registryMCPRouteMCP enrichment blockTool-level denySettings → AI Pilot → MCP Proxy
Upstream OAuth / API keysAIGatewayUpstreamAuthSecret refsUpstream Auth guide
Semantic cache / Redis topologyAIGatewayFilter (semanticCache)Applies obligationsCache & Rate Limits
Guardrails / DLPAIGatewayFilter (guardrails, dlp)EnforcementPolicy decisionsClassifiers/pilot Guardrails & DLP
Per-transaction metricsAIGatewayMetricsPolicyEmits dimensionsObservability settings

Telemetry vs authority: Panels such as Resilience and MCP Proxy on /pilot may show live rollups from ext_proc for observability. BackendTrafficPolicy and MCPRoute remain authoritative for breaker behavior and MCP routing in the gateway runtime.

Next steps

Troubleshooting: If a capability column shows “gateway” but traffic ignores it, confirm the compiled bundle reached the bouncer and that your deployment profile is Kubernetes AI Gateway (Compose profiles may omit some CRD runners). See Troubleshooting.