# Configure external HAProxy for MYSQL cluster

**URL:** <https://forums.percona.com/t/configure-external-haproxy-for-mysql-cluster/27805>\
**Category:** MySQL & MariaDB\
**Tags:** mysql, percona\
**Created:** [January 16, 2024, 12:05pm UTC](https://forums.percona.com/t/configure-external-haproxy-for-mysql-cluster/27805 "2024-01-16T12:05:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pratiyush\_Pushkar](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pratiyush_pushkar/32/14671_2.png) [@Pratiyush\_Pushkar](https://forums.percona.com/u/Pratiyush_Pushkar)\
**Post date:** [January 16, 2024, 12:05pm UTC](https://forums.percona.com/t/configure-external-haproxy-for-mysql-cluster/27805/1 "2024-01-16T12:05:08Z")

</div>

Hi all ,  
We have deployed Percona Mysql Operator and Mysql Cluster on k8 using helm - [link](https://docs.percona.com/percona-operator-for-mysql/pxc/helm.html) . We already have an haproxy configured and running in that cluster . We are thinking to use that to distribute traffic among our percona mysql pods .  
So currently we have set haproxy.enable as well as proxysql.enable to false . So is it possible for us to set our own external haproxy as a proxy for Percona clusters ?

Using operator chart version - 1.13.3  
Using cluster chart version - 1.13.4  
It may require us to create a separate service for each of the pods.

---

<div class="post-metadata">

**Author:** ![lalit.choudhary](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lalit.choudhary/32/51_2.png) [@lalit.choudhary](https://forums.percona.com/u/lalit.choudhary)\
**Post date:** [January 17, 2024, 6:28am UTC](https://forums.percona.com/t/configure-external-haproxy-for-mysql-cluster/27805/2 "2024-01-17T06:28:47Z")

</div>

Hello @Pratiyush_Pushkar

Here documentation for Exposing cluster to external Load balancer,

> **[Percona Operator for MySQL based on Percona Server for MySQL - Exposing the...](https://docs.percona.com/percona-operator-for-mysql/ps/expose.html#exposing-cluster-without-haproxy)**
>
> The Operator provides entry points for accessing the database by client
> applications in several scenarios. In either way the cluster is exposed with
> regular Kubernetes Service objects,
> configured by the Operator.

Other ref: [Custom Resource options - Percona Operator for MySQL based on Percona Server for MySQL](https://docs.percona.com/percona-operator-for-mysql/ps/operator.html#percona-server-for-mysql-section)