All Tools
C
Dev ToolsFreeOpen Source
CONTOUR
Envoy-powered Kubernetes ingress controller
Apache-2.0
ABOUT
Exposing model servers, vector DBs, and internal ML apps on Kubernetes usually means either limited Ingress objects or hand-maintained Envoy configs that drift. Contour sits as a control plane in front of Envoy, translating Kubernetes HTTPProxy and Ingress into live routes with TLS, retries, and weighted routing so inference traffic can be shifted across versions without restarting the data plane by hand.
INTEGRATION GUIDE
1. Route HTTPS traffic to model serving, embedding, and notebook services on Kubernetes
2. Shift a percentage of inference requests to a canary model deployment via HTTPProxy weights
3. Terminate TLS for internal ML APIs and apply retries and timeouts at the Envoy edge
4. Expose multiple RAG or agent backends on one cluster IP with host and path routing
5. Replace ad-hoc Envoy ConfigMaps with Kubernetes-native HTTPProxy objects for ML gateways
TAGS
kubernetesingressenvoyreverse-proxytlstraffic-managementcncf