Caddy Ingress Controller vs Contour
Caddy Ingress Controller
github.comContour
projectcontour.ioSide by side
| Figure | Caddy Ingress Controller | Contour |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Kubernetes Ingress Controllers | 5.7 (#25) | 7.7 (#12) |
Plans
In their own words
Caddy Ingress Controller
Caddy Ingress Controller has no write-up on Specifiction yet; its figures are above.
Contour
Contour is a free, self-hosted, open-source Kubernetes ingress controller that provides the control plane for the Envoy edge and service proxy. It supports Kubernetes Ingress v1, its HTTPProxy custom resource and Gateway API. Contour updates ingress configuration dynamically with minimal dropped connections and supports multiple configuration types in clusters used by multiple teams. It can run as a Kubernetes deployment or daemonset, and administrators can delegate access to wildcard certificates. Documented security features include TLS termination, client authorization, rate limiting, JWT verification and IP filtering. Contour and Envoy expose metrics that Prometheus can scrape, and documentation includes guides for cert-manager, Gatekeeper and AWS Network Load Balancer. The project is tested with Kubernetes 1.21 and later and is intended for both cluster administrators and application developers. Community support is available through the project's GitHub page, where users can report issues or ask questions. Contour is a Cloud Native Computing Foundation incubating project; its documentation includes a threat model, a security reporting process and a security fix checklist.