Contour is a Kubernetes ingress controller that deploys Envoy proxy as a reverse proxy and load balancer.
Contour solves the problem of routing external traffic into Kubernetes clusters by managing Envoy proxy configuration dynamically. Rather than requiring manual proxy updates, Contour watches Kubernetes resources and automatically configures Envoy to reflect changes in services, endpoints, and routing rules. This approach keeps the proxy lightweight while eliminating the gap between desired and actual network state.
Contour suits teams running Kubernetes who need flexible ingress routing without the complexity of a service mesh. The project supports three configuration APIs: the standard Kubernetes Ingress API for basic use cases, HTTPProxy as a custom resource offering richer functionality and solving Ingress design limitations, and the Gateway API emerging from the Kubernetes SIG-Network community. Teams should choose Contour if they want Envoy's capabilities without managing proxy configuration manually, and if they prefer an ingress controller over heavier service mesh solutions.
The project receives issue reports from both core maintainers and external users, indicating real-world adoption without an overwhelming support burden. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker centers on feature requests, bug reports, and user questions, reflecting a mix of enhancement and maintenance activity.
