A Helm chart for installing Percona Server Databases using the PS Operator.
🚀 This release adds calculator-based MySQL configuration, persistent MySQL logs, and custom MySQL users, and hardens asynchronous failover.
Important release notes:
- mysql.autoConfig is enabled by default. The Operator builds the MySQL configuration from the Pod CPU and memory, so both requests and limits must set cpu and memory. Chart defaults are now requests 2 CPU / 4Gi, limits 4 CPU / 8Gi, and a 30Gi data volume (previously a 2Gi request, a 4Gi limit, no CPU request, and a 3Gi volume). To keep a hand-written configuration, set mysql.autoConfig.enabled=false.
- The Fluent Bit log collector is enabled by default and adds log collector and logrotate sidecars to MySQL Pods. To skip them, set logcollector.enabled=false.
- The default Orchestrator failover timeout is 1 hour (previously 6 hours). On timeout the failover is aborted.
Also in this release:
- Custom MySQL users via
users. WhenpasswordSecretRefis omitted, the Operator generates the password and stores it in the<cluster-name>-user-<username>Secret. - A CA bundle for S3-compatible backup storage:
backup.storages.<name>.s3.caBundle, including the binlog server storage. - Extra parameters for the PMM HAProxy client:
pmm.haproxyParams. - Backup start and suspend deadlines:
backup.startingDeadlineSecondsandbackup.suspendedDeadlineSeconds. unsafeFlags.asyncFailoverWithPossibleDataLossfor an asynchronous cluster that runs without backups.- Operator leader election is configurable through
leaderElectionand stays enabled by default. The chart setsPSO_LEADER_ELECTION_*instead of passing--leader-elect. - The operator Role can delete ServiceAccounts and Roles so cluster creation works on OpenShift.
Release notes: PSO 1.3.0