You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When ConfigMap for MySQL config (which is refered in .spec.mysqlConfigMapName) is updated, moco-controller will perform the following operations.
Create a new ConfigMap for my.cnf
Update StatefulSet to use (mount) the new ConfigMap
Delete old ConfigMaps
Currently, the moco-controller does not wait for rolling updates of StatefulSet to delete the old ConfigMap.
Therefore, if a user tries to re-create a pod before the rolling update, the pod will not be created with the following error.
Warning FailedMount 82s (x9 over 3m30s) kubelet MountVolume.SetUp failed for volume "mysql-conf" : configmap "moco-<clustername>.<hash>" not found
Environments
Version: v0.16.1
The text was updated successfully, but these errors were encountered:
Describe the bug
When ConfigMap for MySQL config (which is refered in .spec.mysqlConfigMapName) is updated, moco-controller will perform the following operations.
my.cnf
Currently, the moco-controller does not wait for rolling updates of StatefulSet to delete the old ConfigMap.
Therefore, if a user tries to re-create a pod before the rolling update, the pod will not be created with the following error.
Environments
The text was updated successfully, but these errors were encountered: