# ProxySQL in Percona MySQL operator **URL:** \ **Category:** Percona Operator for MySQL\ **Created:** [May 22, 2025, 10:19am UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060 "2025-05-22T10:19:32Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![reddy\_nishanth](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/reddy_nishanth/32/21004_2.png) [@reddy\_nishanth](https://forums.percona.com/u/reddy_nishanth)\ **Post date:** [May 22, 2025, 10:19am UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/1 "2025-05-22T10:19:32Z")
Hi team, [GitHub - percona/percona-server-mysql-operator: Percona Operator for MySQL](https://github.com/percona/percona-server-mysql-operator), do we have any limitation in supporting ProxySQL proxy? I see for PXC, we do have HAProxy and ProxySQL, but for MySQL operator we only have MySQL router and HAProxy, I wanted to understand the reasons for this. ---
**Author:** ![reddy\_nishanth](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/reddy_nishanth/32/21004_2.png) [@reddy\_nishanth](https://forums.percona.com/u/reddy_nishanth)\ **Post date:** [June 9, 2025, 4:44am UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/2 "2025-06-09T04:44:31Z")
@matthewb , @daniil.bazhenov Any pointers/references here please? ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [June 9, 2025, 4:51pm UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/3 "2025-06-09T16:51:48Z")
ProxySQL should be supported: > **[Build software better, together](https://github.com/search?q=repo%3Apercona%2Fpercona-server-mysql-operator%20proxysql&type=code)** > > GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects. ---
**Author:** ![reddy\_nishanth](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/reddy_nishanth/32/21004_2.png) [@reddy\_nishanth](https://forums.percona.com/u/reddy_nishanth)\ **Post date:** [June 10, 2025, 3:36am UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/4 "2025-06-10T03:36:31Z")
@matthewb Sorry, I’ve seen the custom resource yaml [percona-server-mysql-operator/deploy/cr.yaml at e6fa86c47ed3599f64cad11b438c5aebab43a681 · percona/percona-server-mysql-operator · GitHub](https://github.com/percona/percona-server-mysql-operator/blob/e6fa86c47ed3599f64cad11b438c5aebab43a681/deploy/cr.yaml#L146) and even in the documentation [Design and architecture - Percona Operator for MySQL](https://docs.percona.com/percona-operator-for-mysql/ps/architecture.html) ```auto HAProxy - a load balancing and proxy service compatible with both asynchronous replication and group replication between MySQL instances, MySQL Router - a proxy solution which can be used instead of HAProxy when group replication between MySQL instances is turned on, ``` Looks like it’s not added into CRD ---
**Author:** ![Abhinav\_Gupta](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/abhinav_gupta/32/6262_2.png) [@Abhinav\_Gupta](https://forums.percona.com/u/Abhinav_Gupta)\ **Post date:** [June 11, 2025, 2:30pm UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/5 "2025-06-11T14:30:53Z")
Yes, as of now, Percona operator for MySQL-based (Tech Preview), [only supports the HaProxy and MySQL Router](https://docs.percona.com/percona-operator-for-mysql/ps/architecture.html). Please note that the MySQL-based operator is in tech preview, and it is not recommended for production use yet. If you need it for production use, then use the Percona Operator for MySQL based on PXC, which supports HaProxy and ProxySQL. > **[Comparison with other solutions - Percona Operator for MySQL](https://docs.percona.com/percona-operator-for-mysql/pxc/compare.html#mysql-topologies)** > > There are multiple ways to deploy and manage MySQL in Kubernetes. Here we will focus on comparing the following open source solutions: ![Screenshot 2025-06-11 at 8.00.09 PM](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/c/4/c4f67066130d78ee5d89f06f59eb1842f35c9703.png) ---
**Author:** ![reddy\_nishanth](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/reddy_nishanth/32/21004_2.png) [@reddy\_nishanth](https://forums.percona.com/u/reddy_nishanth)\ **Post date:** [June 13, 2025, 6:26am UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/6 "2025-06-13T06:26:49Z")
@Abhinav_Gupta Firstly, Thanks for the reply We are already using ProxySQL and MySQL as a single instance, for HA, I was looking into Group replication in single primary mode so that it works same as single instance but with High Availability which is also mentioned in [https://www.mysql.com/why-mysql/white-papers/mysql-reference-architectures-for-high-availability/](https://www.mysql.com/why-mysql/white-papers/mysql-reference-architectures-for-high-availability/) Since PXC uses Galera replication, I’m not fully sure whether the transition is worth it. May be it’s simpler to explore to run it with HAProxy But my main query is that, is there any limitation in running Group replication with ProxySQL and hence percona doesn’t support it or just that it’s not implemented yet. Also do we have timeline for MySQL Percona operator to be in 1.0 for Production use? ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [June 13, 2025, 4:13pm UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/7 "2025-06-13T16:13:14Z")
> [@reddy\_nishanth](#): > > I was looking into Group replication in single primary mode so that it works same as single instance but with High Availability This would be the same with PXC. > [@reddy\_nishanth](#): > > Since PXC uses Galera replication, I’m not fully sure whether the transition is worth it. It’s not really a “transition” as PXC is a drop-in replacement. Replace your single instance with PXC, then add node 2, and node 3. Nodes will self-initialize (unlike Group Replication). > [@reddy\_nishanth](#): > > or just that it’s not implemented yet This, yes. HAProxy is far simpler to implement within the operator due to its limited functionality being only a layer 4 port router. Implementing ProxySQL, as a layer 7 protocol router, takes a bit more to get working correctly. As stated, we full support ProxySQL within our PXC Operator so we know it works. It’s just a matter of time, and community desire, to implement ProxySQL within our MySQL Operator. The best HA solution for MySQL is PXC + ProxySQL. ProxySQL is PXC-aware and takes actions based on any PXC changes. ---
**Author:** ![reddy\_nishanth](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/reddy_nishanth/32/21004_2.png) [@reddy\_nishanth](https://forums.percona.com/u/reddy_nishanth)\ **Post date:** [June 14, 2025, 3:05am UTC](https://forums.percona.com/t/proxysql-in-percona-mysql-operator/38060/8 "2025-06-14T03:05:25Z")
Thank you @matthewb for the response, I’ll try PXC and get back in case of issues