Add additional logic to initializing vault

General MR

Summary

Adds further logic to the init container to handle when vault is already initialized. It is worth noting that unsealing vault after a situation where pods get restarted and vault seals itself, outside of a KMS environment this needs to be done manually and the rest of this job will still time out as it did before, but vault functionality will continue as long as unsealing is performed. This is only on a redeployment or other situation where vault seals itself and the init job runs again.

Relevant logs/screenshots

N/A

Linked Issue

issue

Upgrade Notices

N/A

chart/templates/bigbang/autoUnsealAndInit/configmap-for-vault-init.yaml

@@ -28,9 +28,9 @@ data:
       echo "---=== Waiting For Vault Server ===---"; 
       sleep 5; 
     done
-    
+
     echo "---=== Initializing Vault ===---"
-    until vault operator init -address=$VAULT_ADDR > $INIT_OUT; do
+    until vault operator init -address=$VAULT_ADDR > $INIT_OUT || vault operator init -address=$VAULT_ADDR -status; do
       echo "retry initialize"
       sleep 5;
     done