# MySQL 5.7 deployment with Percona Everest

**URL:** <https://forums.percona.com/t/mysql-5-7-deployment-with-percona-everest/38065>\
**Category:** Percona Everest\
**Tags:** mysql\
**Created:** [May 22, 2025, 2:44pm UTC](https://forums.percona.com/t/mysql-5-7-deployment-with-percona-everest/38065 "2025-05-22T14:44:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![an-toine](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@an-toine](https://forums.percona.com/u/an-toine)\
**Post date:** [May 22, 2025, 2:44pm UTC](https://forums.percona.com/t/mysql-5-7-deployment-with-percona-everest/38065/1 "2025-05-22T14:44:30Z")

</div>

Hello,

We are currently evaluating Percona Everest to migrate some legacy databases.

For a first POC, we have deployed Everest 1.6.0 on one of our Vanilla Kubernetes cluster.

When creating a new MySQL server, there is no option to instanciate a MySQL 5.7 database in the `Database version` dropdown.  
I know MySQL 5.7 is EOL but we have to temporarily support it for business constraints.

Is this a limitation of the product or do we have to allow the deployment of legacy databases engines somewhere in settings ?

Regards,  
Antoine

---

<div class="post-metadata">

**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:** [May 22, 2025, 3:46pm UTC](https://forums.percona.com/t/mysql-5-7-deployment-with-percona-everest/38065/2 "2025-05-22T15:46:12Z")

</div>

Hello @an-toine,  
As you know 5.7 is EOL. In fact, it is now almost 2 years EOL. Furthermore, 8.0 will EOL next year. Your business constraints are falling far behind! 🙂

As you noted, there is no option for 5.7 in Everest, and there are no plans to add it since it is so old.