You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We did a test disaster recovery run and identified some documentation points that should be clarified (as identified by other posters previously, see end of post). We got over all of those issues however and successfully recovered our DB from our backups. We did however encounter some issues even with the DB being restored.
After the restore the PWs of configured DB users were no longer working. The operator did not ensure they were set to the correct values as specified in the pre-existing secrets, nor did it generate new secrets.
Further we encountered some issues with our Harbor deployment. The OAuth client secret, replication secrets and user CLI secrets were all invalid and had to be manually reset.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all
We did a test disaster recovery run and identified some documentation points that should be clarified (as identified by other posters previously, see end of post). We got over all of those issues however and successfully recovered our DB from our backups. We did however encounter some issues even with the DB being restored.
After the restore the PWs of configured DB users were no longer working. The operator did not ensure they were set to the correct values as specified in the pre-existing secrets, nor did it generate new secrets.
Further we encountered some issues with our Harbor deployment. The OAuth client secret, replication secrets and user CLI secrets were all invalid and had to be manually reset.
Is this the expected behaviour after a restore?
Our config:
Documentation updates:
Beta Was this translation helpful? Give feedback.
All reactions