# Percona operator for ProxySQL without XtraDB **URL:** \ **Category:** ProxySQL\ **Created:** [May 5, 2024, 7:58pm UTC](https://forums.percona.com/t/percona-operator-for-proxysql-without-xtradb/30059 "2024-05-05T19:58:03Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![qonalex](https://avatars.discourse-cdn.com/v4/letter/q/898d66/32.png) [@qonalex](https://forums.percona.com/u/qonalex)\ **Post date:** [May 5, 2024, 7:58pm UTC](https://forums.percona.com/t/percona-operator-for-proxysql-without-xtradb/30059/1 "2024-05-05T19:58:03Z")
Hello! We are going to use ProxySQL with our current MySQL server. Is this possible to use Percona Operator for MySQL for ProxySQL deployment purposes only? So we need to have Percona operator-managed ProxySQL cluster with external mysql server. ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [May 5, 2024, 8:51pm UTC](https://forums.percona.com/t/percona-operator-for-proxysql-without-xtradb/30059/2 "2024-05-05T20:51:54Z")
Hey @qonalex . It is not something that our operator was designed for. Apart from disabling xtrabackup you would need to somehow rework discovery and config generation. ProxySQL is not that complex to disable. Why not using some helm chart? ---
**Author:** ![qonalex](https://avatars.discourse-cdn.com/v4/letter/q/898d66/32.png) [@qonalex](https://forums.percona.com/u/qonalex)\ **Post date:** [May 6, 2024, 3:46am UTC](https://forums.percona.com/t/percona-operator-for-proxysql-without-xtradb/30059/3 "2024-05-06T03:46:32Z")
I’ve found one more less alive: [charts/dysnix/proxysql at main · dysnix/charts · GitHub](https://github.com/dysnix/charts/tree/main/dysnix/proxysql) But their approach to store secrets requires additional work to be done.