[Bug] my.cnf should be mutable about mariadb-operator

[mmontes11]

Hey there!

100% this should be mutable at some point.

Updating the my.cnf config will need a Pod restart to pick up the new changes, so the plan is to keep it inmutable until we support custom upgrades:

• #321

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[rammelmueller]

Same problem here. We're using ArgoCD to deploy the MariaDB instance and we're a bit lost. What would be the standard way to update the my.cnf when using the operator?

[mmontes11]

Hey there @rammelmueller ! Sorry for the late response.

At the moment, the spec.myCnf is inmutable for a reason: after updating the config, a restart of the cluster needs to happen for the changes to have effect, which means the operator would need to trigger a rolling upgrade.

The default rolling upgrade of the StatefulSet is not reliable enough, we need to implement something custom, see:

• #321

We will look into it shortly, and then we can make spec.myCnf mutable.

[rammelmueller]

Thanks for the reply @mmontes11!

It's OK for now, I guess, however, one question remains: What is the standard procedure to updated the spec.myCnf when using some gitops tool like ArgoCD?

[mmontes11]

spec.myCnf is inmutable as I said, which means that the wehook will not allow ArgoCD to update this field. There is however one workaround, which implies using StatefulSet rolling upgrade, so use it at your own risk:

• As you can see, the operator creates a ConfigMap to store the my.cnf which is mounted by the StatefulSet

spec:
  image: mariadb:11.2.2
  myCnf: |
    [mariadb]
    bind-address=*
    default_storage_engine=InnoDB
    binlog_format=row
    innodb_autoinc_lock_mode=2
    max_allowed_packet=256M
  myCnfConfigMapKeyRef:
    key: my.cnf
    name: mariadb-config

• You may patch this ConfigMap from ArgoCD, the operator won't interact with it once it is created
• Then, you should trigger a rolling upgrade. You will need to dynamically upgdate the Pod template from ArgoCD. Something equivalent to:

kubectl patch sts mariadb  -p "{\"spec\":{\"template\":{\"metadata\":{\"labels\":{\"date\":\"`date +'%s'`\"}}}}}"

This will be handled by the operator in the next few releases. The idea is that spec.myCnf becomes mutable and the ConfigMap gets updated, triggering a custom upgrade done by the operator.

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.