vault-armada-app/vault-helm
Tae Park 896008fb73 vault-manager wait for one server only when initialized
Modifying the vault-manager initialization logic so that it only waits
for pod number equal to the replica value to be active
if the raft is not yet initialized.

TEST PLAN:
 - In a 2 controller, 1 worker setup,
 - Upload and apply vault
 - Lock the host that vault-manager is running on
 - Vault manager should restart
 - Within the logs, there should not be a repetition of " Waiting for sva-vault statefulset running pods..."
 - Vault Sanity test in AIO-SX
 - Bashate of rendered init.sh

Closes-bug: 2029375

Signed-off-by: Tae Park <tae.park@windriver.com>
Change-Id: I41990b87395a5d5364ef91c048f740d0f0675d6b
2023-08-08 15:31:29 -04:00
..
debian update vault helm chart to 0.24.1 2023-06-14 15:05:32 -04:00
vault-helm vault-manager wait for one server only when initialized 2023-08-08 15:31:29 -04:00