Description:
I'm using MySQL Operator to manage MySQL InnoDB instances on Kubernetes. The issue I'm facing is that when the MySQL Operator restarts, it generates a new random password for the mysqladmin user.
However, my InnoDB instances are mounted to existing data volumes and try to use the previously set password. This results in an "access denied" error because the passwords are now mismatched between the MySQL Operator and the InnoDB instances.
How can I prevent the MySQL Operator from changing the mysqladmin password after a restart, or synchronize the passwords so that the existing InnoDB instances can connect properly? Any suggestions would be greatly appreciated.
I manually set the mysqladmin password in the MySQL Operator configuration file, expecting that it would retain the same password across restarts. However, the Operator still generated a new random password upon restart, leading to access denied errors for the existing InnoDB instances.
Additionally, I tried setting the password using Kubernetes Secrets and deployed the InnoDB Operator using Helm, but the issue persisted. Each time the Operator restarted, it still generated a new password, resulting in the same problem.
How to repeat:
The above issue describes a problem with managing MySQL InnoDB instances using the MySQL Operator in a Kubernetes environment. Specifically, each time the MySQL Operator restarts, it generates a new random password for the mysqladmin user. However, the existing InnoDB instances are using previously set passwords with their mounted data volumes, leading to "access denied" errors due to password mismatches.
To resolve this issue, the goal is either to prevent the MySQL Operator from changing the mysqladmin password after a restart or to find a way to synchronize the passwords between the MySQL Operator and the existing InnoDB instances.
