-
Bug
-
Resolution: Done
-
Major
-
quay-v3.4.0
-
False
-
False
-
Undefined
-
Description:
This is an issue found when trying to upgrade quay V3.3.2 operator to the latest V3.4.0 quay TNG operator, following TNG Operator guide, found with "spec.quay.database.credentialsSecretKey", TNG Operator can't start the migration for managed postgresql databse, the correct reference should be "spec.quay.database.credentialsSecretName"
Also pls add the required steps to guide to show Quay customers how to create new secret, give examples here:
oc create secret generic quaydb --from-literal=database-root-password=postgresql
Pls update the TNG Operator guide.
If using an Operator-managed database, ensure that the password is set for the postgres root admin user (not set by default). This allows remote access to the database for migration. The Operator looks for this password in the Secret referenced by spec.quay.database.credentialsSecretKey under the database-root-password key.
Docs:
https://docs.openshift.com/container-platform/4.6/operators/admin/olm-upgrading-operators.html