Kong Ingress Controller review
A free, extensible choice for Kong-centered Kubernetes API platforms.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Kong Ingress Controller runs Kong Gateway in Kubernetes and translates Kubernetes Ingress, HTTPRoute, and other Gateway API resources into Kong Gateway configuration. It is designed for platform and infrastructure teams managing Kubernetes clusters and API traffic. The controller supports HTTP, TCP, UDP, and TLS routing, load balancing across Kubernetes service endpoints, active and passive health checking, weighted traffic distribution, authentication, authorization, rate limiting, and plugin-based request processing. It can be installed with Helm or the Kong Operator and deployed with self-managed Kong Gateway or Kong Konnect environments.
Its strongest fit is breadth within the Kong ecosystem. Integrations include Kong Gateway, Kong Konnect, Kong Operator, cert-manager, Istio, Prometheus, and Grafana. TLS certificate rotation through cert-manager adds an automation path for certificate operations, while Kong plugins extend rate limiting, authentication, authorization, and request processing. The controller also supports both Ingress and Gateway API models, giving teams a choice between established Kubernetes resources and newer Gateway API resources. These capabilities make it suitable for teams that want ingress routing tied to a wider API management platform rather than an isolated traffic entry point.
The open-source model and free plan make Kong Ingress Controller accessible for self-hosted Kubernetes deployments. Its trade-off is an operating model built around Kong Gateway and related platform components, which may be more than a small team needs for straightforward ingress. Kubernetes-native canary deployments should use Gateway API; Kong documents the Canary Release plugin as unsuitable for that use. Choose Kong Ingress Controller when Kong integrations, policy plugins, and multi-service traffic control are priorities. Consider a narrower controller when the requirement is limited to basic routing with minimal platform scope.
Kong Ingress Controller pros and cons
- Where it wins
- Supports both Kubernetes Ingress and Gateway API resources
- Combines routing, health checks, rate limiting, auth, and TLS handling
- Connects with Kong Gateway, Konnect, Operator, and cert-manager
- Where it doesn't
- The Kong Canary Release plugin is not suitable for Kubernetes-native use
- Its Kong ecosystem model may exceed simple ingress requirements
- Custom plugins and broad policy controls suit platform teams more than casual use
Kong Ingress Controller 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