Changing the database password is not totally unlike an upgrade of Usage Engine. It requires you to stop the platform and batch workflows, changing the password and then upgrading the helm charts.
Make sure all ECs are disconnected.
To change the database password the platform must be stopped. We do this by setting replicas to 0.
Verify that the platform pod have stopped by checking that there is no platform appearing after the command below.
Upgrade the Usage Engine helm chart either by editing the kubernetes env-secrets or by passing the arguments with helm.
Refer to Bootstrapping System Certificates and Secrets - Private Cloud[hide]2.0[/hide] if you opt for editing the kubernetes env-secrets. When done, continue with step 5.
The password must be entered in base64 encoded format
If you choose to pass arguments with helm then you need to make sure that you also pass any arguments you passed in when Usage Engine was installed. The example below we have installed the Usage Engine chart as "mz-chart" from the path "mz-path".
Increase the replica count again.
Once the platform have restarted a new password will be set. If the platform pod is ready you have verified that the password works.