A10 Thunder Kubernetes Connector vs BFE Ingress Controller
A10 Thunder Kubernetes Connector
documentation.a10networks.com
BFE Ingress Controller
bfe-networks.netSide by side
| Figure | A10 Thunder Kubernetes Connector | BFE Ingress Controller |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Kubernetes Ingress Controllers | 7.7 (#11) | 9.0 (#2) |
| Integrations | A10 says the solution supports automation tools such as Terraform and Ansible for integration into CI/CD pipelines. | Official documentation names Kubernetes, Prometheus, Jaeger, Fluentd and mainstream layer-4 load balancers as integrations. |
| 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 directs questions and issues to GitHub and lists CNCF Slack and WeChat community channels. |
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.
BFE Ingress Controller
BFE Ingress Controller is an open-source Layer 7 load balancer derived from Baidu’s proprietary Baidu Front End. It is self-hosted and supports Linux, macOS, Windows, and API use. BFE handles HTTP, HTTPS, SPDY, HTTP/2, WebSocket, TLS, gRPC, and FastCGI traffic; HTTP/3 is planned. Operators define content-based routing rules with a domain-specific language. Traffic features include global and distributed load balancing, zone-aware balancing, resilience to zone-level failures, and overload protection. Each tenant has an isolated configuration that is not visible to other tenants. A built-in plugin framework supports extensions for traffic management, security, and observability. For operations, BFE provides subsystem metrics, troubleshooting and analysis logs, and distributed tracing. The project lists integrations with mainstream Layer 4 load balancers and ecosystem projects such as Kubernetes, Prometheus, Jaeger, and Fluentd. It is licensed under Apache 2.0 and is a CNCF sandbox project. Documentation covers installation from source and through binary, Go, Snap, and Docker paths. The open-source plan is free.