You are browsing documentation for an outdated version. See the latest documentation here.

FAQs

Why EndpointSlices and not Services?

The Kong Ingress Controller does not use Services to route traffic to the pods. Instead, it uses the EndpointSlice API (which is available since Kubernetes v1.21) to bypass kube-proxy to allow Kong features such as 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?

In version 0.5.0 and later, the Kong Ingress Controller tags each entity that it manages inside Kong’s database and only manages the entities that it creates. This means that if consumers and credentials are created dynamically, they are not deleted by the Ingress Controller.