Bug #108812 Mysql operator doesn't update serverConfig settings provided in innodbcluster

• Submitted: 18 Oct 2022 18:31
• Modified: 19 Oct 2022 5:37
• Reporter: Ales Verbic (OCA)
• Status: Verified
• Category: MySQL Operator
• Severity: S4 (Feature request)
• Version: 8.0.30 - 2.0.5
• OS: Any
• CPU Architecture: Any
• Tags: 8.0.30:2.0.5

[18 Oct 2022 18:31] Ales Verbic

Description:
When you specify 'my.cnf' settings in innodbcluster resource those values are only used at initial creation of innodbcluster.

If you want to change update my.cnf settings config map doesn't get updated and statefulset is not restarted to pickup new config map settings

How to repeat:
Create innodbcluster use helm chart specify

serverConfig:
   mycnf: |
   [mysqld]
   max-connection=300

update

serverConfig:
   mycnf: |
   [mysqld]
   max-connection=400

there is no change in config map and statefulset doesn't doesn't get restarted to pickup new config map

Suggested fix:
Operator should read and innodbcluster resource and check for diffs in serverConfig and update config map and restart the cluster.

[19 Oct 2022 5:37] MySQL Verification Team

Thank you for the feature request.