1. Proposed title of this feature request
Document migration instructions for moving from community External Secrets Operator (ESO) to RH ESO

2. What is the nature and description of the request?
My customer and others use External Secrets Operator per Red Hat’s recommendations (e.g., here and here) to a) synchronize secrets from a secure external store and b) enable them to record secret configuration in a GitOps-style repo securely. Today they use either the community-maintained operator available via OLM and OperatorHub as documented here or with a Helm chart as documented here.

Once RH publishes a supported OLM operator and instance of ESO as planned in https://issues.redhat.com/browse/OCPSTRAT-1539 these customers want to migrate from the community projects to RH-supported ones. This should be relatively straightforward, as the same CRDs will be used, but will probably require modifying the “managed-by” and similar annotations on some resources.

This RFE is to request that Red Hat document the process of migration from the community projects to the RH-supported ones, perhaps as a Solution at https://access.redhat.com/solutions. Thank you!

3. Why does the customer need this? (List the business requirements here)
Customer plans to implement community-supported Helm chart today for immediate use and wants to migrate in a supported way to RH-supported solution once it is available.

4. List any affected packages or components.
External Secrets Operator instance and OLM operator, see: https://issues.redhat.com/browse/OCPSTRAT-1539.