All the maintained options below are open source; commercial editions (F5 NGINX 75 Plus, Kong Enterprise, Traefik 27,315 Hub) add support and policy features:
| Option | Speaks | License | Latest (Sep 2026) | Good fit |
|---|---|---|---|---|
| cloud-provider-kind 508 | Ingress, Gateway API | Apache-2.0 | 0.11.1 | kind 14,561 clusters |
| Envoy Gateway 117,531 | Gateway API | Apache-2.0 | 1.9.1 | Self-managed clusters |
| NGINX Gateway Fabric 1,169 | Gateway API | Apache-2.0 | 2.7.2 | Teams that know NGINX |
| Traefik | Ingress, Gateway API | MIT | 3.7.13 | k3s 51,195 (bundled), small clusters |
| Cilium 96,364 | Gateway API, Ingress | Apache-2.0 | 1.20.2 | Clusters on Cilium CNI |
BookNest uses the Gateway API: new features land there, routes carry over between implementations, and TLS and path rules need no annotations. On kind the implementation is cloud-provider-kind, as kind's documentation recommends, so nothing extra runs in the cluster; on EKS 24 , GKE 1 or AKS 6 (Managed Kubernetes) the same HTTPRoute attaches to the provider's GatewayClass, with only gatewayClassName changing. An Ingress on a maintained controller is still fine for simple sites; an ingress-nginx installation is a migration to schedule.