openstack-armada-app/python-k8sapp-openstack
Mihnea Saracin fc68439414 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 and mariadb services cannot use this approach because
they are unable to work properly if their replica number
is decreased from 2 to 1. So a kubernetes toleration
is used here to allow the rabbitmq and mariadb pods to be
deployed on the locked controller.

Change-Id: I15cf2a3f62525751435ddbe66760935f3ab21d2b
Closes-Bug: 1879018
Signed-off-by: Mihnea Saracin <Mihnea.Saracin@windriver.com>
2020-09-11 18:46:52 +03:00
..
centos Enable helm/armada plugin delivery with the application 2020-05-27 15:05:02 -04:00
k8sapp_openstack Fix apply of stx-openstack when host is locked 2020-09-11 18:46:52 +03:00