このページは、まだ日本語ではご利用いただけません。翻訳中です。

旧バージョンのドキュメントを参照しています。 最新のドキュメントはこちらをご参照ください。

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.

Is it possible to deploy Kong Ingress Controller with Kong Gateway as DaemonSet?

You can deploy Kong Gateway as a DaemonSet instead of a Deployment. This runs a Kong Gateway Pod on every kubelet in the Kubernetes cluster. These Pods can use the network of the host they run on instead of a dedicated network namespace. This allows Kong to bind ports directly to the Kubernetes nodes’ network interfaces, without the extra network translation imposed by NodePort Services. Learn more in the dedicated Helm chart docs section.