# Kong Manager in Kubernetes won't work

**URL:** <https://discuss.konghq.com/t/kong-manager-in-kubernetes-wont-work/9103>\
**Category:** General\
**Tags:** kubernetes, kong-gateway\
**Created:** [September 27, 2021, 11:40pm UTC](https://discuss.konghq.com/t/kong-manager-in-kubernetes-wont-work/9103 "2021-09-27T23:40:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![traines](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/traines/32/158_2.png) [@traines](https://discuss.konghq.com/u/traines)\
**Post date:** [October 12, 2021, 8:57pm UTC](https://discuss.konghq.com/t/kong-manager-in-kubernetes-wont-work/9103/3 "2021-10-12T20:57:33Z")

</div>

How are you accessing the admin API and ? You have the proxy set to a LoadBalancer, which will allocate an externally-accessible IP in most cases, but use `admin.localhost` and `manager.localhost` as the Ingress hostnames. I’d normally only expect those to work if you have port-forwarded to the proxy and set up local DNS entries to route those hostnames to localhost (i.e. through the port forward).

For Manager to work, it needs to know a valid URL for the admin API, and the admin API needs to know the URL used to access the GUI to set CORS headers. Those are set via these settings:

> **[Configuration Reference for Kong Gateway (Enterprise) - v2.5.x | Kong Docs](https://docs.konghq.com/enterprise/2.5.x/property-reference/#admin_gui_url)**
>
> Documentation for Kong, the Cloud Connectivity Company for APIs and Microservices.

> **[Configuration Reference for Kong Gateway (Enterprise) - v2.5.x | Kong Docs](https://docs.konghq.com/enterprise/2.5.x/property-reference/#admin_api_uri)**
>
> Documentation for Kong, the Cloud Connectivity Company for APIs and Microservices.

When enabled, the `ingress.hostname`, `ingress.path`, and protocol settings will configure those settings automatically. For example, since you have TLS disabled, the chart will set `KONG_ADMIN_GUI_URL=http://manager.localhost/`.

If you’re not actually using those Ingresses to access those resources, those settings will be misconfigured, and Manager won’t actually be able to reach the admin API. I’d recommend either:

- Mapping DNS to point to the proxy LoadBalancer IP and configuring the chart Ingress settings to use that hostname, and then access Manager via that hostname.
- Manually setting `env.admin_gui_url` and `env.admin_api_uri` (which will override the auto-generated configuration) to reflect whatever URLs you’re actually using to reach those resources.

If you’re still not seeing data, reviewing your browser developer console and network diagnostics should clarify exactly what’s failing.

---

_[View the full topic](https://discuss.konghq.com/t/kong-manager-in-kubernetes-wont-work/9103)._