Comment 23 for bug 1855474

Reviewed: https://review.opendev.org/699532
Committed: https://git.openstack.org/cgit/starlingx/openstack-armada-app/commit/?id=6538342c26c479988fbf8515260ee76e2809bc08
Submitter: Zuul
Branch: master

commit 6538342c26c479988fbf8515260ee76e2809bc08
Author: Hu, Yong <email address hidden>
Date: Wed Dec 18 02:23:44 2019 +0000

    Update mariadb chart to enable probe overrides

    Adding probes parameters for armada overriding them in duplex AIO and
    multi-node deployment. Specifically, there are 2 mariadb-servers in
    the DB cluster for OpenStack services at duplex or multi-node cases.
    These 2 mariadb-server pods are placed on Controller-0 and Controller-1
    respectively (manipulated by anti-affinity). Whenever one Controller is
    rebooted on purpose or even worse accidiently shutdown for any reasons
    mariadb-server pod on that controller is gone together. To keep mariadb
    cluster still working even with only one instance, we have to adjust
    the default probe behaviors. Upon this request, we have to export probe
    parameters for "startupProbe" and "readinessProbe" so that StarlingX
    Armada application could set these parameters accordingly and thereby
    mariadb server can still work as expected with even only one pod in the
    cases of Controller node rebooting or shutdown.

    Closes-bug: 1855474

    Change-Id: I3a8a99edd44d7ac4257ddf79b6baba5c52714324
    Signed-off-by: Hu, Yong <email address hidden>
    Co-Authored-By: Zhipeng, Liu <email address hidden>