1. Proposed title of this feature request

oc-mirror v2: Set "updateStrategy" fields in CatalogSource object

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

Users that mirror operators into offline or disconnected environments will be updating the operator index images as well. Many customers will check the OpenShift web console UI's "OperatorHub" section to see the new operators. CatalogSource objects for the index image have an "updateStrategy" field that determines how often OpenShift will poll the container registry for an updated catalog index container images.

The default polling rate is 15 minutes. This rate is not defined in the CatalogSource CRD object. The only way to know this is to check the olm github source code repository.

The CatalogSource yaml that oc-mirror creates during the m2d process does not contain the "updateStrategy" fields. When the yaml is applied to the cluster, OLM does not fill in the default values. This can be confirmed by extracting the CatalogSource yaml from the cluster after applying the yaml generated by oc-mirror.

Users are left wondering when the catalog index image, and the operators show in the OpenShift web console, will change. This causes users to wonder if there was an error in the mirror or upload process.

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

Customers that mirror content into offline or air-gapped environments need to be able to clearly understand when the operator index image will rotate after pushing new content into the private registry with oc-mirror. This will avoid cases where the index does not update for 15 minutes and customers are left wondering if there was an error with the mirroring process.

4. List any affected packages or components.

oc-mirror