HackMDOverview
Two topics, since the relevant functionality was delivered in two parts
- support for a new
olm.csv.metadataFBC object to convery packagemanifest information; and - support to update old FBC catalogs to use the new metadata, as
opm render --migrate
1. packagemanifest data formats served by opm
opm serve facilitates operator console visibility, provided by the grpc packagemanifest API.
opm was updated to provide a more efficient FBC representation of the data in olm.csv.metadata, versus old olm.bundle.object.
The change was part of
We maintain backwards compatibility, so all future versions can serve old/new packagemanifest data. Older opm versions do not know how to serve the new format and discard it.
Therefore, operators contributing new-format metadata in catalogsources served by older versions of opm are not visible to the console or oc get packagemanifests cli.
OLM does not rely on the packagemanifest data, so opm validate does not fail if it is missing.
The current 4.15 build of ose-operator-registry provides opm 59aa935eb (correlating to this). It is newer than 17ee584, so they generate the new olm.csv.metadata packagemanifest info (but can serve older olm.bundle.object).
Availability
- upstream
- v1.28.0 or later
- downstream
2. opm render migrate support
This was a separate PR to support opm render --migrate command to convert an existing FBC to the latest format.
Availability
- upstream
- downstream
