Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

A10 Thunder Kubernetes Connector review

#25 of 28 in Kubernetes Ingress Controllers

A strong fit for Kubernetes teams already operating A10 Thunder ADC.

6.8/10Editor score
A10 Thunder Kubernetes Connector6.8 Visit A10 Networks

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

A10 Thunder Kubernetes Connector runs inside a Kubernetes cluster and monitors applications, services, and pods. It processes Kubernetes Ingress resources and automatically updates A10 Thunder ADC to route external traffic to Kubernetes workloads. The product is aimed at organizations running enterprise Kubernetes applications with A10 Thunder ADC for traffic management, security, and centralized visibility across public, private, hybrid, or multi-cloud environments.

Its main strength is the connection between Kubernetes application state and A10 ADC configuration. Custom resource definitions support A10 load-balancing objects, while external load balancing handles traffic entering Kubernetes applications. Application and bandwidth rate limiting are available through the A10 solution, and centralized traffic visibility and troubleshooting are provided through Thunder ADC. Terraform and Ansible integrations also fit teams that manage infrastructure and deployment workflows through automation. Prometheus and Grafana are listed integrations for monitoring and visualization workflows.

The product makes the most sense when A10 Thunder ADC is already part of the environment, because the connector's value depends on that platform and some security or traffic-management capabilities may depend on licensed ADC modules. The published pricing model is contact sales, so buyers will need a product discussion to understand licensing. A self-hosted deployment suits organizations that want control within their Kubernetes environment, but it also places infrastructure management with the customer. Teams seeking Kubernetes Ingress processing without an A10 ADC dependency, or a directly comparable public price, should consider another option.

A10 Thunder Kubernetes Connector pros and cons

  • Where it wins
    • Automates Thunder ADC updates from Kubernetes application state
    • Supports Ingress processing, external load balancing, and rate limiting
    • Connects with Terraform, Ansible, Prometheus, and Grafana
  • Where it doesn't
    • Requires A10 Thunder ADC for its core traffic-management role
    • Self-hosted deployment requires Kubernetes infrastructure management
    • Contact-sales pricing makes cost comparison less direct

A10 Thunder Kubernetes Connector fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update