-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
None
Feature Overview
As a oc-mirror user, I would like mirrored operator catalogs to reflect the mirrored operators only, so that, after I mirror my catalog I can check that it contains the filtered operators using:
$ oc-mirror list operators --catalog mirror.syangsao.net:8443/ocp4/redhat/redhat-operator-index:v4.12
Context
In oc-mirror v2 (and in v1 after bug fix OCPBUGS-31536), oc-mirror doesn't rebuild catalogs.
- The filtered declarative config isn't recreated based on the imagesetconfig filter
- The catalog cache isn't regenerated
- The catalog image isn't rebuilt based on the above 2 elements
Instead, the original catalog image is pushed as is to the mirror registry. Its declarative config will show all operators, and for each operator all channels and all bundles.
This behavior is causing some inconvenience to our users.
Concerns, complexity
- How to deal with caches
- How to deal with default channels
- How to deal with keeping a single valid channel head
- What to do when cross channel filtering is involved
Known ongoing/related work
- https://github.com/operator-framework/operator-registry/pull/1231/files
- https://docs.google.com/document/d/1jWRBZNPtMMbzAz71hjCKubrL_dxOBUs11xUe3QUnozo/edit
- CLID-151
- CLID-86
- CLID-87
Additional info:
- https://redhat-internal.slack.com/archives/C02JW6VCYS1/p1719601148099479
- https://redhat-internal.slack.com/archives/C02JW6VCYS1/p1719908123474019
- causes
-
RFE-5688 oc-mirror does not rebuild catalog post mirroring.
- Accepted
- is depended on by
-
OCPSTRAT-1426 [GA] OC mirror v2
- In Progress
- is related to
-
RFE-5581 Catalog filtering based on Channel/MinVerson criteria
- Under Review
- relates to
-
OCPSTRAT-1372 Operator Framework provides catalog content filtering API
- New
-
OCPSTRAT-1373 OC Mirror integration with OLM catalog filtering tool / library
- New
- links to