Kong's Kubernetes ingress controller. Routes HTTP into a cluster using Kong Gateway for the data path.
Kong Ingress Controller (Apache-2.0) is the pick when you want Kong Gateway features (rate limiting, auth plugins, request transformation) at the ingress layer rather than deploying Kong as a sidecar. Config via standard Kubernetes Ingress + Kong CRDs. Alternatives: ingress-nginx (ubiquitous, simpler), Traefik (service discovery across orchestrators), Contour (Envoy-based, Project Contour).
Each bar is this project's percentile among all 152 CE projects for that signal — 80% means it beats 4 out of 5 projects on that axis. Grade is an equal-weighted composite. Reddit mindshare lands here next; HN already contributes.
docker pull kong/kubernetes-ingress-controller:3.5.14 docker pull kong/kubernetes-ingress-controller:3.4.21 docker pull kong/kubernetes-ingress-controller:3.5.13 docker pull kong/kubernetes-ingress-controller:3.5.12 docker pull kong/kubernetes-ingress-controller:3.5.11 No comments yet. Be the first.