I’m reading the following on Kong-ingress docs: “The Kong 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 achieve the same Services usage avoidance without the Kong-ingress container? Just with plain Kong.
The major option I demand on is cookie-based session stickiness.