Skip to content

Features

Nantian Gateway combines standard Kubernetes Gateway API routing with experimental extension APIs for AI traffic, token-aware policy, Wasm plugins, and backend load-balancing policy. This section gives each major capability a direct entry point.

You want to…Use this
Route HTTP traffic by host, path, headers, or queryHTTPRoute
Route gRPC traffic by service and methodGRPCRoute
Handle raw TCP or UDP connectionsTCPRoute, UDPRoute
Pass through TLS without terminationTLSRoute
Encrypt backend connections with custom CAsBackendTLSPolicy
Distribute traffic across multiple backendsTraffic Splitting
Protect backends from overloadCircuit Breaker
Control request ratesToken Policy
Proxy requests to AI model providersAI Gateway
Redact PII in AI requestsPII Masking
Cache AI responses for repeat promptsSemantic Cache
Extend the proxy with custom logicWasm Plugins
Monitor traffic and gateway healthMetrics & Grafana
Reference backends across namespacesReferenceGrant
AreaPrimary APIsStabilityStart here
Traffic routingGateway, HTTPRoute, GRPCRoute, TCPRoute, UDPRoute, TLSRouteGateway API standard or alpha, depending on resourceTraffic Management
AI trafficAIService, TokenPolicyExperimental Nantian APIAI Gateway
Custom proxy logicWasmPluginExperimental Nantian APIWasm Plugins
Backend policyBackendLBPolicyExperimental Gateway API policyTraffic Management
Security and operationsBackendTLSPolicy, ReferenceGrant, Admin API, metricsMixed stable and extended APIsSecurity And Observability

These resources are the default way to configure Nantian Gateway. They follow the upstream Gateway API specification and are portable across compliant implementations.

ResourcePurposeExample
GatewayClassIdentifies the controllerspec.controllerName: nantian-gw
GatewayEntry point with listenersPort 80 HTTP, port 443 HTTPS with TLS
HTTPRouteHTTP routing rulesPath /api → backend api-svc:8080
GRPCRoutegRPC routing rulesService echo.Echo → backend grpc-svc:9090
TCPRouteRaw TCP forwardingPort 3306 → MySQL backend
UDPRouteUDP packet forwardingPort 53 → DNS backend
TLSRouteTLS passthroughSNI *.example.com → backend
BackendTLSPolicyBackend TLS validationVerify backend cert against custom CA
ReferenceGrantCross-namespace accessAllow route in team-a to use service in team-b

For field-level details, see Gateway API Resources. For a comparison of which features are supported versus other implementations, see the Gateway API Support Matrix.

Nantian Gateway also ships experimental extension APIs. These are namespaced under gateway.nantian.dev and require explicit opt-in.

ResourcePurposeExample
AIServiceAI provider/model targetRoute to OpenAI GPT-4o with API key from Secret
TokenPolicyToken/request quotasLimit route to 1000 requests per minute
WasmPluginSandboxed Wasm moduleAdd custom auth header to all requests on a Gateway
BackendLBPolicyBackend load balancingRound-robin with session cookie persistence

Read Experimental Features before using these APIs, then use Custom And Experimental Resources for current field references.

Features move from experimental to stable on independent timelines. Use this table to gauge readiness for production:

FeatureStatusAPI VersionProduction Ready?
HTTP/HTTPS RoutingStablegateway.networking.k8s.io/v1✅ Yes
GRPCRouteStablegateway.networking.k8s.io/v1✅ Yes
TLS PassthroughStablegateway.networking.k8s.io/v1✅ Yes
TCP/UDP RoutingAlphagateway.networking.k8s.io/v1alpha2⚠️ With testing
BackendTLSPolicyStablegateway.networking.k8s.io/v1✅ Yes
AI GatewayExperimentalgateway.nantian.dev/v1alpha1⚠️ Production evaluation
TokenPolicyExperimentalgateway.nantian.dev/v1alpha1⚠️ Production evaluation
WasmPluginExperimentalgateway.nantian.dev/v1alpha1⚠️ Development/Staging
BackendLBPolicyExperimentalgateway.networking.k8s.io/v1alpha2⚠️ Production evaluation
RoutePolicyExperimentalgateway.nantian.dev/v1alpha1⚠️ Production evaluation

Features marked ⚠️ “Production evaluation” are under active development. Their APIs may change between releases. Test thoroughly in staging before production deployment.