The conversion to file-based catalogs impacts the following actions:
build new catalogs from scratch and/or modify and re-publish catalogs using OPM.
filter catalogs for content via OPM or scripts.
directly interact with the SQLite database inside the catalog image such as doing SQL queries or running OPM commands.
prune catalogs for disconnected usage.
query catalog content outside the cluster.
debug the index catalog images.
You are likely not impacted if you are only using catalog images to:
mirror them for disconnected clusters using $ oc adm catalog mirror
create catalog sources for OLM (to consume the RedHat Index catalog via OLM on the clusters)
Or if you only distribute your Operators by creating a PR in its repositories. Nothing will change for you at the first moment. You will still be publishing your projects as you have been using the PR-based contribution process in this project.
On Feb. 8th: The v4.11 tag of the RedHat Community index image (https://registry.redhat.io/redhat/community-operator-index:v4.11) will be using the file-based catalogs. (All other tags will keep using the existing SQLite format)
✨ The change to file-based catalogs is a largely transparent change:
There are no changes to the bundle format.
Workflows for publishing operators to these catalogs will not change.
Connected install workflows will not change.
The impact is limited to the following workflows:
building new catalogs by modifying and re-publishing catalogs using OPM.
filtering catalogs for content via OPM or scripts (such as opm index prune)
directly interacting with the SQLite database inside the catalog image such as doing SQL queries against it.
mirroring catalogs for disconnected usage.
For more details, please see the following announcements:
For RedHat Community: https://github.com/redhat-openshift-ecosystem/community-operators-prod/discussions/512