Comment 7 for bug 1879018

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

commit 754a1d33de7e16b454052190a2496f1a1d59c707
Author: Mihnea Saracin <email address hidden>
Date: Thu Jul 23 16:39:05 2020 +0300

    Fix apply of stx-openstack when host is locked

    Currently, all of the stx-openstack services have the
    replica count set to the number of the controllers.
    If one of the controllers is locked their replicas
    number will still be 2 which is incorrect.
    We solve this by changing the number of replicas
    to be equal to the number of the active controllers.
    The rabbitmq service cannot use this approach because
    it is unable to work properly if its replicas number
    is decreasaed from 2 to 1. So a kubernetes toleration
    is used here to allow the second rabbitmq pod to be
    deployed on the locked controller.

    Change-Id: Ie979c7b5f2755ad673bd180e38b68e0d53c5f9b2
    Closes-Bug: 1879018
    Signed-off-by: Mihnea Saracin <email address hidden>