Migrating from a Quay Standalone Multicloud Object Gateway (MCG) to an ODF StorageCluster-Managed MCG - NooBaa

Issue

It has been previously shown in the Quay Documentation to deploy a NooBaa MCG stack using a NooBaa CR yaml instead of a storagecluster.yaml or going through the ODF UI to create the standalone MCG. This is no longer supported and has been shown to cause issues during the ODF v4.18 - ODF v4.19 upgrade, as demonstrated in the Standalone MCG Deployed via Quay docs fails ODF upgrade to 4.19 solution.

If this configuration is discovered and can be easily identified with an empty storagecluster.yaml in the openshift-storage namespace, it will be required to migrate this configuration before the upgrade to ODF v4.19.

RELATED ARTICLES:
Standalone MCG Deployed via Quay Documentation Fails ODF v4.19 Upgrade