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:
I’ve set stripPath to false which has allowed me to remove the NGINX container. However, Kong is still returning the binary files of the application not rendering the page. Any ideas?
When I curl the endpoint I get this:
curl -I http://$PROXY_IP/oauth/admin
curl: (8) Weird server reply
I get a binary file back. When I set the path to a CSS file in pingfederate Kong returns that like I’d expect from a standard API call. When I hit the standard /oauth/admin endpoint it can’t seem to figure out how to return the other files.
I’ve put ping federate behind a load balancer and it is rendering fine. I’m guessing it must be how pingfederate is returning files Kong can’t understand it?
Okay, can you share the Ingress and KongIngress resource that you’ve created to proxy this traffic? It seems like a configuration error in one of those two.