Skip to content

Autopilot Mode: Self-Tuning MySQL Configuration #197

Description

@hors

Which operator(s) is this request for?

  • Percona Operator for MySQL (PS)

Why this matters
Tuning MySQL for containerized environments requires deep expertise that most teams do not have in-house: default configurations waste the resources you pay for, while manual tuning is error-prone and goes stale the moment workloads or resources change. With Autopilot Mode, the operator automatically derives a production-grade MySQL configuration from each cluster's actual CPU, memory, and workload profile, and re-tunes it whenever resources change, so every cluster runs optimally without a DBA hand-crafting settings. This turns Percona into a self-tuning database platform on Kubernetes, delivering the operational simplicity of cloud DBaaS offerings while remaining fully open source and running on your own infrastructure.

Image

Community Note

  • Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, as they generate noise and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    DevOpsMySQLLabel for MySQLOperatorsLabel for Percona Kubernetes OperatorsPSLabel for Percona Server for MySQLProposed

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions