A10 Thunder Kubernetes Connector vs Contour
A10 Thunder Kubernetes Connector
documentation.a10networks.comContour
projectcontour.ioSide by side
| Figure | A10 Thunder Kubernetes Connector | Contour |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Kubernetes Ingress Controllers | 7.7 (#11) | 7.7 (#12) |
| Integrations | A10 says the solution supports automation tools such as Terraform and Ansible for integration into CI/CD pipelines. | Contour documentation includes guides for cert-manager, Gatekeeper, AWS Network Load Balancer, and Prometheus metrics. |
| Purpose | Thunder Kubernetes Connector (TKC) helps provide external access to applications running in a Kubernetes cluster with Thunder ADC. | Contour is an open source Kubernetes ingress controller that provides the control plane for the Envoy edge and service proxy. |
| Support | A10 provides product technical support and says its Technical Assistance Center uses a follow-the-sun support model to address issues at any time of day. | The project provides community support through its GitHub project page and invites users to file issues or ask questions there. |
Plans
In their own words
A10 Thunder Kubernetes Connector
A10 Thunder Kubernetes Connector (TKC) monitors Kubernetes application lifecycles and updates an external Thunder ADC load balancer to route traffic. Running inside a Kubernetes cluster, it identifies a web service’s NodePort and dynamically configures Thunder ADC to load-balance traffic to Kubernetes nodes, avoiding manual network-resource provisioning. A10 describes TKC for multi-cloud and hybrid-cloud deployments, where Thunder ADC can apply consistent security and business policies across public and private clouds. Centralized traffic routing provides operations teams with application traffic and analytics visibility for troubleshooting. TKC supports Terraform and Ansible for CI/CD integration and is listed as an automated Kubernetes service-discovery option. Related Thunder ADC capabilities include Layer 4–7 load balancing, customizable health checks, aFleX scripting, TLS/SSL offloading, rate limiting and a web application firewall. TKC v2.4.2 is documented for Linux, self-hosted deployments using the ingress API model.
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.