# Kong Manager with Ingress

**URL:** <https://discuss.konghq.com/t/kong-manager-with-ingress/5568>\
**Category:** Questions\
**Tags:** kubernetes\
**Created:** [February 18, 2020, 7:38pm UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568 "2020-02-18T19:38:36Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_O\_Connor](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/mike_o_connor/32/1667_2.png) [@Mike\_O\_Connor](https://discuss.konghq.com/u/Mike_O_Connor)\
**Post date:** [February 18, 2020, 7:38pm UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/1 "2020-02-18T19:38:36Z")

</div>

Hi there,

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:

manager:  
tls:  
enabled: false  
type: NodePort  
ingress:  
enabled: true  
path: /manager

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?

---

<div class="post-metadata">

**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\
**Post date:** [February 18, 2020, 11:35pm UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/2 "2020-02-18T23:35:45Z")

</div>

You need to set KONG\_ADMIN\_GUI\_URL

> **[Open-Source API Management and Microservice Management](https://docs.konghq.com/enterprise/1.3-x/kong-manager/networking/configuration/)**
>
> Secure, Manage & Extend your APIs or Microservices with plugins for authentication, logging, rate-limiting, transformations and more.

---

<div class="post-metadata">

**Author:** ![Mike\_O\_Connor](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/mike_o_connor/32/1667_2.png) [@Mike\_O\_Connor](https://discuss.konghq.com/u/Mike_O_Connor)\
**Post date:** [February 19, 2020, 3:34pm UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/3 "2020-02-19T15:34:31Z")

</div>

I did as you suggested, but that did not resolve the issue.

---

<div class="post-metadata">

**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\
**Post date:** [February 19, 2020, 3:49pm UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/4 "2020-02-19T15:49:29Z")

</div>

Please share your kong environment variable settings.

---

<div class="post-metadata">

**Author:** ![shubham.hatwar](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@shubham.hatwar](https://discuss.konghq.com/u/shubham.hatwar)\
**Post date:** [June 26, 2020, 7:24am UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/5 "2020-06-26T07:24:52Z")

</div>

> [@hbagdi](#):
>
> KONG\_ADMIN\_GUI\_URL

I am also facing the same issue but insted of /manager i used /

also attached the network logs

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/konghq/original/2X/d/d6421c63d5f5f20f5cb777664316e555eb8db6a2.png)

Below are the my configuration details.  
values.yml:  
env:  
database: “postgres”  
nginx\_worker\_processes: “1”  
proxy\_access\_log: /dev/stdout  
admin\_access\_log: /dev/stdout  
admin\_gui\_access\_log: /dev/stdout  
rbac\_auth\_header: Kong-Admin-Token  
portal\_api\_access\_log: /dev/stdout  
proxy\_error\_log: /dev/stderr  
portal\_api\_error\_log: /dev/stderr  
prefix: /kong\_prefix/  
admin\_listen: 0.0.0.0:8001  
admin\_gui\_url: [http://x.x.x.x:80/](http://x.x.x.x:80/)  
pg\_user: kongcp  
pg\_host: x.x.x.x  
pg\_port: 5432  
pg\_database: xxxxxx  
pg\_password: xxxxxx  
password:  
valueFrom:  
secretKeyRef:  
name: kong-enterprise-superuser-password  
key: password

manager:  
enabled: true  
type: NodePort  
annotations: {}  
http:  
enabled: true  
servicePort: 8002  
containerPort: 8002  
parameters:   
tls:  
enabled: false  
servicePort: 8445  
containerPort: 8445  
ingress:  
enabled: true  
hostname:  
annotations:  
[kubernetes.io/ingress.class:](http://kubernetes.io/ingress.class:) “gce”  
[kubernetes.io/ingress.global-static-ip-name:](http://kubernetes.io/ingress.global-static-ip-name:) “kongs-static-ip”  
path: /

---

<div class="post-metadata">

**Author:** ![Satwant\_Singh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/satwant_singh/32/2048_2.png) [@Satwant\_Singh](https://discuss.konghq.com/u/Satwant_Singh)\
**Post date:** [June 26, 2020, 8:39pm UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/6 "2020-06-26T20:39:15Z")

</div>

@shubham.hatwar remove the last “/” from admin\_gui\_url: [http://x.x.x.x:80](http://x.x.x.x:80)

---

<div class="post-metadata">

**Author:** ![shubham.hatwar](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@shubham.hatwar](https://discuss.konghq.com/u/shubham.hatwar)\
**Post date:** [June 29, 2020, 7:44am UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/7 "2020-06-29T07:44:57Z")

</div>

Hi But still the problem is not solved.

Getting below error while access the kong-manager from Browser,but when i do curl will get 200 OK Response code.

#kong/ha# curl -v x.x.x.x

- Rebuilt URL to: x.x.x.x/
- Trying x.x.x.x …
- TCP\_NODELAY set
- Connected to x.x.x.x (x.x.x.x) port 80 (#0)

> GET / HTTP/1.1  
> Host: x,.x.x.x  
> User-Agent: curl/7.52.1  
> Accept: _/_

\< HTTP/1.1 200 OK  
\< Server: openresty  
\< Date: Mon, 29 Jun 2020 07:28:49 GMT  
\< Content-Type: text/html; charset=UTF-8  
\< Content-Length: 19392  
\< Last-Modified: Sat, 30 May 2020 01:04:00 GMT  
\< Cache-Control: no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0  
\< X-Frame-Options: sameorigin  
\< X-XSS-Protection: 1; mode=block  
\< X-Content-Type-Options: nosniff  
\< X-Permitted-Cross-Domain-Policies: master-only  
\< Accept-Ranges: bytes  
\< Via: 1.1 google

Kindly find the below configuration details and attached error screenshots.

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/konghq/original/2X/3/33aaf021736cba7703a3acd69bf754b314eb0c56.png)

configuration:

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/konghq/original/2X/4/4a9928e7f4755c36c1b1fe96a1e1e75d51b7fd05.png)

values.yml  
env:  
database: “postgres”  
nginx\_worker\_processes: “1”  
proxy\_access\_log: /dev/stdout  
admin\_access\_log: /dev/stdout  
admin\_gui\_access\_log: /dev/stdout  
rbac\_auth\_header: Kong-Admin-Token  
portal\_api\_access\_log: /dev/stdout  
proxy\_error\_log: /dev/stderr  
portal\_api\_error\_log: /dev/stderr  
prefix: /kong\_prefix/  
admin\_listen: 0.0.0.0:8001  
admin\_gui\_url: [http://x.x.x.x:80](http://x.x.x.x:80)  
pg\_user: kongcp  
pg\_host: x.x.x.x  
pg\_port: 5432  
pg\_database: xxxxxx  
pg\_password: xxxxxx  
password:  
valueFrom:  
secretKeyRef:  
name: kong-enterprise-superuser-password  
key: password

---

<div class="post-metadata">

**Author:** ![Satwant\_Singh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/satwant_singh/32/2048_2.png) [@Satwant\_Singh](https://discuss.konghq.com/u/Satwant_Singh)\
**Post date:** [June 29, 2020, 1:31pm UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/8 "2020-06-29T13:31:12Z")

</div>

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](http://x.x.x.x:8002)

> <https://github.com/Kong/charts/blob/master/charts/kong/README.md#service-location-hints>

Kong property file reference

> **[Open-Source API Management and Microservice Management](https://docs.konghq.com/enterprise/1.5.x/property-reference/#kong-manager)**
>
> Secure, Manage & Extend your APIs or Microservices with plugins for authentication, logging, rate-limiting, transformations and more.

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](mailto: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.

---

<div class="post-metadata">

**Author:** ![shubham.hatwar](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@shubham.hatwar](https://discuss.konghq.com/u/shubham.hatwar)\
**Post date:** [June 30, 2020, 7:11am UTC](https://discuss.konghq.com/t/kong-manager-with-ingress/5568/9 "2020-06-30T07:11:01Z")

</div>

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](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

Below Attached code for ingress.yml and value.yml  
values.yml  
env:  
database: “postgres”  
nginx\_worker\_processes: “1”  
proxy\_access\_log: /dev/stdout  
admin\_access\_log: /dev/stdout  
admin\_gui\_access\_log: /dev/stdout  
rbac\_auth\_header: Kong-Admin-Token  
portal\_api\_access\_log: /dev/stdout  
proxy\_error\_log: /dev/stderr  
portal\_api\_error\_log: /dev/stderr  
prefix: /kong\_prefix/  
admin\_listen: 0.0.0.0:8001  
admin\_gui\_url: [http://x.x.x.x:8002](http://x.x.x.x:8002)  
ing.yml  
apiVersion: extensions/v1beta1  
kind: Ingress  
metadata:  
annotations:  
[kubernetes.io/ingress.class:](http://kubernetes.io/ingress.class:) gce  
[networking.gke.io/suppress-firewall-xpn-error:](http://networking.gke.io/suppress-firewall-xpn-error:) “true”  
creationTimestamp: “2020-06-30T05:17:56Z”  
finalizers:

- [networking.gke.io/ingress-finalizer](http://networking.gke.io/ingress-finalizer)  
generation: 1  
labels:  
[app.kubernetes.io/instance:](http://app.kubernetes.io/instance:) my-kong  
[app.kubernetes.io/managed-by:](http://app.kubernetes.io/managed-by:) Helm  
[app.kubernetes.io/name:](http://app.kubernetes.io/name:) kong  
[app.kubernetes.io/version:](http://app.kubernetes.io/version:) “2”  
helm.sh/chart: kong-1.5.0  
name: my-kong-kong-manager  
namespace: apim-kong-admin  
resourceVersion: “18483876”  
selfLink: /apis/extensions/v1beta1/namespaces/apim-kong-admin/ingresses/my-kong-kong-manager  
uid: aeec7ce8-d975-4272-8e75-5b19a8da7c91  
spec:  
rules:
- http:  
paths:
  - backend:  
serviceName: my-kong-kong-manager  
servicePort: 8002  
path: /