A10 Thunder Kubernetes Connector vs HAProxy Ingress
A10 Thunder Kubernetes Connector
documentation.a10networks.comHAProxy Ingress
haproxy-ingress.github.ioSide by side
| Figure | A10 Thunder Kubernetes Connector | HAProxy Ingress |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Kubernetes Ingress Controllers | 7.7 (#11) | 7.6 (#13) |
| Purpose | Thunder Kubernetes Connector (TKC) helps provide external access to applications running in a Kubernetes cluster with Thunder ADC. | HAProxy Ingress configures HAProxy to route incoming requests from an external network to applications in a Kubernetes cluster. |
| 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 lists a Kubernetes Slack channel, a users mailing list, and Stack Overflow for community discussion and questions. |
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.
HAProxy Ingress
HAProxy Ingress is a free, self-hosted controller that configures HAProxy to route external requests to applications in a Kubernetes cluster. It applies changes made in the cluster to HAProxy without requiring a separate update process. The project supports Ingress and Gateway API resources and describes more than 200 configuration options. Gateway API support is partial: the documented implementation covers GatewayClass, Gateway, TCPRoute, and HTTPRoute, but not HTTPRoute filters or resource status updates. Installation uses a Helm chart and requires Helm 3, a running Kubernetes cluster, and administrative privileges in that cluster. Version 0.16 requires Kubernetes 1.21 or newer. Local cluster options named by the project include minikube, kind, k3s, k3d, and colima. It associates requests with ingress hosts using TLS SNI and the Host header. Metrics can be collected with Prometheus and Grafana using Prometheus Operator. The project uses the Apache-2.0 license and lists community channels including Slack, a users mailing list, and Stack Overflow.