A10 Thunder Kubernetes Connector vs NetScaler Ingress Controller
A10 Thunder Kubernetes Connector
documentation.a10networks.comNetScaler Ingress Controller
docs.netscaler.comSide by side
| Figure | A10 Thunder Kubernetes Connector | NetScaler Ingress Controller |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Linux | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 0 |
| Spec score · Kubernetes Ingress Controllers | 7.7 (#11) | 7.1 (#20) |
| Headquarters | San Jose, California, United States | Fort Lauderdale, Florida, USA |
| Integrations | A10 says the solution supports automation tools such as Terraform and Ansible for integration into CI/CD pipelines. | The documentation includes integration guidance for Prometheus and Grafana, cert-manager, HashiCorp Vault, ExternalDNS, and OpenShift. |
| Pricing | The opened A10 pages do not state a price for Thunder Kubernetes Connector. | NetScaler’s pricing page lists subscription license options but directs buyers to contact a representative or service provider for pricing details. |
| Purpose | Thunder Kubernetes Connector (TKC) helps provide external access to applications running in a Kubernetes cluster with Thunder ADC. | The controller translates Kubernetes Ingress rules into configuration for NetScaler load balancers and routes traffic into Kubernetes clusters. |
| 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. | NetScaler support experts follow up on support tickets submitted through the Citrix support portal, and users can also ask the NetScaler community. |
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.
NetScaler Ingress Controller
NetScaler Ingress Controller has no write-up on Specifiction yet; its figures are above.