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
use system MariaDBAccount for the galera server's root pw
This commit ties together the previous ones to create a new
MariaDBAccount when a Galera instance is created, and then to
use the password from that account/secret in the mariadb
bootstrap/maintenance scripts.
Galera gets bootstrapped with this secret, then the mariadbaccount
controller, who is waiting for galera to be available to set up this
new "root" account, wakes up when galera is running, and changes
the root password to itself, establishing the initial job hash
for the mariadbaccount.
As we now have a mariadbaccount linked to the outermost lifecycle
of a galera instance, some hardening of the deletion process has been
added to clarify that mariadbaccount will run deletion jobs only if
Galera is not marked for deletion. If galera is marked for deletion,
then we have to assume the service/pods are gone and no more drops can
take place, even if the Galera CR is still present (chainsaw
conveniently adds its own finalizer to Galera when running, preventing
it from being fully deleted, which exposed this issue).
Additional changes to the mysql_root_auth.sh and account.sh scripts
allow for in-place changes of root password.
As there are now chainsaw tests that update the root password, a new
cleanup step is added to all the chainsaw tests that cleans out
existing volumes (deletes /var/lib/mysql), deletes volume claims
and releases them from the volume. There cannot be leakage of volume
data between tests now that the root password may not match the
initial password, as the controller re-uses this data and then
can't bootstrap.
Co-Authored-By: Claude <[email protected]>
0 commit comments