1. Proposed title of this feature request

RH OLM Operator for External Secrets Operator (ESO)

2. What is the nature and description of the request?

Create and support an OLM operator for External Secrets Operator (https://github.com/external-secrets/external-secrets). Also support AWS Secrets Manager and GitHub Actions secrets providers with ESO.

Upstream support for this operator has been discontinued, see https://github.com/external-secrets/external-secrets-helm-operator/issues/81

3. Why does the customer need this? (List the business requirements here)

Customer securely stores secret API keys, passwords, and private certificate keys in a store outside of OpenShift - AWS Secrets Manager and GitHub (Actions) - and needs a secure way to synchronize, rotate and use them from OpenShift operators and applications. Customer also wants to be able to refer to and configure these secrets and their use declaratively in a GitOps repo.

Red Hat SMEs have recommended External Secrets Operator (ESO) for this purpose and customer is pleased with this option. But upstream support for this operator has been discontinued, see https://github.com/external-secrets/external-secrets-helm-operator/issues/81. Customer also strongly prefers to use a RH-supported solution and not a community/upstream project.

4. List any affected packages or components.

OpenShift Secrets. 

ESO is also useful for integrating OpenShift with Hashicorp Vault.