ModelsAgree
← All leaderboards
🚪

Best Kubernetes ingress controller

3 models · updated 2026-07-09

The verdict

Traefik leads — 1 of 3 models rank Traefik the top pick.

Not unanimous: ChatGPT picks NGINX Ingress Controller; Gemini picks Cilium.

Combined ranking

  1. 1
    Traefikincumbent—13 pts
    GPT #2Claude #1Gemini #2

    The default landing spot for teams fleeing the retired ingress-nginx (EOL March 2026); dead-simple CRD/middleware model, native Gateway API support, automatic Let's Encrypt, huge Helm/community footprint, and a smooth OSS-to-enterprise path

    To stay #1 Close the raw-throughput and tail-latency gap vs Envoy/HAProxy-based dataplanes at very high RPS

  2. 2
    Ciliumincumbentnew8 pts
    GPT —Claude #3Gemini #1

    Unmatched eBPF-powered routing performance, Hubble-driven observability, and kernel-level security that bypasses kube-proxy.

    To rank higher Simplify setup complexity and consolidate its large CRD footprint.

  3. 3
    NGINX Ingress Controllerincumbent▲18 pts
    GPT #1Claude —Gemini #3

    broadest production adoption, huge Kubernetes ecosystem support, strong HTTP/TLS performance, mature annotations, Helm charts, docs, and troubleshooting knowledge

    To rank higher unify its legacy Ingress strength with first-class Gateway API support and a cleaner security/configuration model

  4. 4
    Kong Ingress Controllerincumbentnew6 pts
    GPT #4Claude #4Gemini #4

    best when ingress is also API management, with strong plugins for auth, rate limiting, transformations, observability, and enterprise governance

    To rank higher reduce operational complexity and overhead for teams that only need straightforward ingress routing

  5. 5
    Envoy Gatewayincumbent▼25 pts
    GPT —Claude #2Gemini #5

    The CNCF-blessed, Gateway API-first successor pattern; Envoy's battle-tested dataplane, first-class HTTPRoute/GRPCRoute support, vendor-neutral governance, and it's where upstream investment is clearly flowing in 2026

    To rank higher Mature the extension/policy ecosystem (rate limiting, auth plugins) so common edge features don't require custom EnvoyPatchPolicy surgery

  6. 6
    HAProxy Kubernetes Ingress Controller▼44 pts
    GPT #3Claude #5Gemini —

    excellent raw performance, predictable latency, mature load-balancing behavior, strong TCP/HTTP features, and reliable production operations

    To rank higher make configuration, documentation, and Kubernetes-native UX as approachable as Traefik or NGINX

  7. 7
    Contournew1 pts
    GPT #5Claude —Gemini —

    clean Envoy-based design, solid Gateway API support, simple architecture, good multi-team delegation model, and less baggage than heavier API gateways

    To rank higher build a larger ecosystem and stronger commercial/support story to compete with NGINX, Traefik, Kong, and HAProxy

Rank history

123456706-2906-3007-0707-08TraefikCiliumNGINX Ingress ControllerKong Ingress ControllerEnvoy GatewayHAProxy Kubernetes Ingress ControllerContour
Traefik#1Cilium#2NGINX Ingress Controller#3Kong Ingress Controller#4Envoy Gateway#5HAProxy Kubernetes Ingress Controller#6Contour#7

By model

ChatGPT

  1. 1.NGINX Ingress Controller
  2. 2.Traefik
  3. 3.HAProxy Kubernetes Ingress Controller
  4. 4.Kong Ingress Controller
  5. 5.Contour

Claude

  1. 1.Traefik
  2. 2.Envoy Gateway
  3. 3.Cilium
  4. 4.Kong Ingress Controller
  5. 5.HAProxy Kubernetes Ingress Controller

Gemini

  1. 1.Cilium
  2. 2.Traefik
  3. 3.NGINX Ingress Controller
  4. 4.Kong Ingress Controller
  5. 5.Envoy Gateway

Tracked by ModelsAgree · rank 1 = 5 pts … rank 5 = 1 pt · re-polled continuously