Michel Thebeau f994829fcb override pre-existing anti-affinity
commit f7a37e6a, "Removing default injector anti-affinity rules",
disables anti-affinity for the injector pod.  This is sufficient for
future application updates.  However, during application-update an old
pod that still has anti-affinity will still prevent scheduling of a new
pod.  This is observed on AIO-SX when testing application-update in
preparation for USM.

Using injector.strategy.rollingUpdate.maxUnavailable
(DeploymentStrategy) set to 100% the old pod will immediately terminate
while the new pod waits for its termination.

This is the workaround described in the original in starlingx bug:
https://bugs.launchpad.net/starlingx/+bug/2030901.

Test Plan:
PASS  AIO-SX vault sanity
PASS  application-update

Partial-Bug: 2030901
Story: 2011073
Task: 50484

Change-Id: I66fe336ece7f1ccd68caa665aabc693f1b9a5c18
Signed-off-by: Michel Thebeau <Michel.Thebeau@windriver.com>
2024-06-28 20:58:00 +00:00
2023-12-18 15:34:44 -06:00
2020-07-02 09:08:19 +00:00
2020-07-09 11:18:44 -04:00
2020-07-09 11:18:44 -04:00
2023-12-18 15:34:44 -06:00
Description
StarlingX Vault App
1.9 MiB
Languages
Python 74.7%
Makefile 19%
Dockerfile 4.7%
Smarty 1.3%
Assembly 0.2%
Other 0.1%