![Hu, Yong](/assets/img/avatar_default.png)
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 <yong.hu@intel.com> Co-Authored-By: Zhipeng, Liu <zhipengs.liu@intel.com>
This repo is for https://github.com/openstack/openstack-helm-infra
Changes to this repo are needed for StarlingX and those changes are not yet merged. Rather than clone and diverge the repo, the repo is extracted at a particular git SHA, and patches are applied on top.
As those patches are merged, the SHA can be updated and the local patches removed.