I am running kong enterprise in k8s. I have a load balancer proxy service and ingress enabled for kong manager. I’m using the official helm chart to deploy kong enterprise and I have the manager service configured like so:
This works great - I’m able to hit the manger service with a browser: https://$PROXY_IP/manager
Unfortunately, I get a blank page and inspection of the network tab shows that my manager service is not adding /manager to the path when pulling resources. For example, https://$PROXY_IP/fonts/Roboto-Bold.woff?v=2.137 should be https://$PROXY_IP/manager/fonts/Roboto-Bold.woff?v=2.137. This is one of MANY network calls that are failing. How do I configure the manager service so that it knows to prefix manager to the path?
looks like your Kong Manager is exposed on port 8002.
So you probably want to correct that in the admin_gui_url. http://x.x.x.x:8002
Kong property file reference
Also if you using Kong Manager you are enterprise customer please open a support ticket with your support account.Or you might be able to send a email to support@konghq.com
Using that channel will make sure your enterprise SLA are met on any tickets you open and its a private channel as well.
Hi , I am using the the Google Ingress to expose kong outside the kubernetes and in gke ingress port is 80 with ingress ip , so that i have to mention in admin_gui_url. http://1.2.3.4.80
as ingress is listen on port 80 and then in ingress i configure the backend as manager service. And also I change the configuration with port x.x.x.x:8002 but still the issue is same, but curl give me 200 OK response code but when check in UI some 404 error are there