Skip to content

Update mariadb-operator v0.28.1 - #124

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
mariadb-operator-new
May 9, 2024
Merged

Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
mariadb-operator-new

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented May 9, 2024 •

Copy link
Copy Markdown
Member

Update of mariadb-operator which solves problem with not working mysql-exporter

@kvaps Andrei Kvapil (kvaps) changed the title mariadb operator new Update mariadb-operator v0.28.1 May 9, 2024

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice minor updates

Marian Koreniuk (themoriarti) pushed a commit to themoriarti/cozystack that referenced this pull request Oct 10, 2026
mariadb-operator up to v0.0.27 mounted the referenced ConfigMap key as
/etc/mysql/conf.d/my.cnf whatever the key was called. Since v0.0.28 the
file takes the key's own name, so the chart's key "config" became
/etc/mysql/conf.d/config, and the server's !includedir reads only *.cnf
files from that directory. Every setting in the chart's my.cnf has been
ignored since that operator bump: instances run on stock defaults,
including a 128M InnoDB buffer pool inside the 128Mi default limit.

Renaming the key restores the file as intended. Existing instances roll
their pods once, since the projected volume in the pod template changes,
and come back with the chart's settings in effect, including sql-mode
and innodb_flush_log_at_trx_commit, not only the resource sizing.

Fixes: a9c42c8 ("Update mariadb-operator v0.28.1 (cozystack#124)")
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants