Kong's Kubernetes Ingress Controller v2.0.0 is currently in beta. Check out the
beta documentation and try out
v2.0.0 for yourself.
Why endpoints and not services?
The Kubernetes Ingress Controller does not use
Services to route traffic
to the pods. Instead, it uses the Endpoints API
to bypass kube-proxy
to allow Kong features like session affinity and
custom load balancing algorithms.
It also removes overhead
such as conntrack entries for iptables DNAT.
Is it possible to create consumers using the Admin API?
From version 0.5.0 onwards, the Kubernetes Ingress Controller tags each entity
that it manages inside Kong’s database and only manages the entities that
This means that if consumers and credentials are created dynamically, they
won’t be deleted by the Ingress Controller.