# Use health check for kong-proxy

**URL:** <https://discuss.konghq.com/t/use-health-check-for-kong-proxy/13361>\
**Category:** Questions\
**Created:** [February 13, 2025, 2:16pm UTC](https://discuss.konghq.com/t/use-health-check-for-kong-proxy/13361 "2025-02-13T14:16:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ImthiyazAhamed](https://avatars.discourse-cdn.com/v4/letter/i/58f4c7/32.png) [@ImthiyazAhamed](https://discuss.konghq.com/u/ImthiyazAhamed)\
**Post date:** [February 13, 2025, 2:16pm UTC](https://discuss.konghq.com/t/use-health-check-for-kong-proxy/13361/1 "2025-02-13T14:16:57Z")

</div>

have deployed Kong using a Helm chart and configured the `kong-proxy` with a custom internal load balancer IP. Now, I need to expose `kong-proxy` externally through an Azure Application Gateway. However, I’m facing challenges in configuring the health probe for the the Application Gateway with the exposed IP of proxy-lb created with helm chart.

When running a `curl` command from a pod within the same namespace (`curl http://<POD_IP>:8100/status`), I receive a `200 OK` response. However, I haven’t found a similar health check endpoint for the `kong-proxy` lb service.

Any suggestions on how to configure a suitable health probe for the `kong-proxy` service?

Note: We are using kong in hybrid mode and Control Plane Is in Kong Connect. We are only deploying the Data plane. So we don´t have the adminAPI enabled