Hey folks!
Okay, so if you’ve switched from a Standalone k8s deployment to a ReplicaSet recently, and getting this error, this one’s for ya!
For each deployment, you’ll get a new root password in the corresponding secret. Though the value of this secret gets updated every time you redeploy your ReplicaSet, the change won’t take any effect, since ReplicaSets are based on k8s statefulsets, thus if the PVC’s Reclaim Policy is “Delete”, it won’t get deleted by default, after you delete your deployment with e.g. helm. Which means your “admin” DB and the storedKey (root-password) within, is going to be the same as it was for the first time/deployment. If you want the changes to take effect, you’ll need to clean up the PVC resource manually. (Maybe the PV and the physical storage as well…)
I think it’s a bug after all. If the root-password is coming from the secret, it should get updated each time I deploy, independently of previous storage states.