1. Proposed title of this feature request

Make External Secrets Operator available for OpenShift 4.18

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

With OpenShift 4.19 Red Hat introduced the External Secrets Operator (ESO) Tech Preview. Because OpenShift 4.18 is the current EUS version and we can expect that many customers will be using it in production for longer period of time it is requested by some to have the ESO available from the Operator Catalog for OpenShift 4.18 too.

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

Deploying ESO on older version of OpenShift requires to use Helm which is not compatible with some automation approaches. It blocks customers in using ESO.

4. List any affected packages or components.

• External Secrets Operator