VladPolskiy/mariadb-operator
1
0
Fork 0
mirror of https://github.com/mariadb-operator/mariadb-operator.git synced 2025-07-22 13:04:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated release notes

Browse Source
This commit is contained in:
mmontes11
2024-09-13 16:35:43 +02:00
parent 302670fc3a
commit fe56e1b0de
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/releases/RELEASE_v0.0.31_HEADER.md.gotmpl
View File

@ -1,10 +1,10 @@
This is a patch release to fix some regressions related to the Galera. If you are using Galera with `ReadWriteOnce` storage, it is highly recommended to upgrade. Please, follow the __[UPGRADE GUIDE](https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/UPGRADE_v0.0.31.md)__.
When using `ReadWriteOnce` storage, if the Galera recovery `Jobs` (introduced in [v0.0.30](https://github.com/mariadb-operator/mariadb-operator/releases/tag/v0.0.30)) are not scheduled in the same node as the `MariaDB` `Pods`, they will be unable to attach the PVC and the recovery will not progress. See the following issues for further detail: https://github.com/mariadb-operator/mariadb-operator/issues/840
When using `ReadWriteOnce` storage, if the Galera recovery `Jobs` (introduced in [v0.0.30](https://github.com/mariadb-operator/mariadb-operator/releases/tag/v0.0.30)) are not scheduled in the same node as the `MariaDB` `Pods`, they won't be able to attach the PVC and the recovery will not progress. See the following issues for further detail: https://github.com/mariadb-operator/mariadb-operator/issues/840
By default, we have configured `podAffinity` to the recovery `Jobs` to make sure the attachment succeeds. See the PR: https://github.com/mariadb-operator/mariadb-operator/pull/843
In addition, we have also fixed another regression that prevents the operator from polling after the related `MariaDB` resource has been deleted. See the PR: https://github.com/mariadb-operator/mariadb-operator/pull/832
In addition, we have also fixed another regression that prevents the operator from polling after the related `MariaDB` resource has been deleted. See the PR: https://github.com/mariadb-operator/mariadb-operator/pull/832
Finally, to better support large fleets of databases, we are introducing support for `MaxConcurrentReconciles`, defaulting to `10` for `MariaDB` and `MaxScale` resources: https://github.com/mariadb-operator/mariadb-operator/pull/833