We’ve recently adopted the use of Kong in our Kubernetes cluster using the Kong ingress controller. We’re hoping to be able to use Kong for all of our gateway requirements.
I have an authentication server running on /oauth/admin this routes traffic to the service. Here is my ingress:
Whenever I hit that endpoint Kong returns a binary file. When I add an NGINX container to the pod it works but is very slow. I’ve seen that you can change the
nginx_kong.lua to get around this in Kong outside of Kubernetes ( https://docs.konghq.com/0.11.x/configuration/#serving-both-a-website-and-your-apis-from-kong) but nothing for the ingress controller.
Have I missed something or is it not possible?