As of today, only label-type bundle properties are accepted in the CSV properties annotation when added to an index. Accepting arbitrary types during index addition will allow bundles that specify OpenShift compatibility to be included in an index.

This is stopgap for bundle authors and will be superseded by https://issues.redhat.com/browse/OLM-2130.

See Also:

• https://github.com/operator-framework/operator-registry/blob/88eda1a2c6dab32c5a049a286259f3c0f713587e/pkg/sqlite/load.go#L938

Why does this need to be released in 4.8?

There will be a breaking API change introduced in 4.9.0: v1beta1 CRDs are removed. Many optional operators deployed by OLM still use v1beta1 CRDs.

In order to prevent an upgrade from 4.8 to 4.9 that results in breaking these operators, at minimum we need:

• A way for operator authors to signify which minor versions of OpenShift their operator is compatible with
• OLM to signal to CVO – the thing that controls cluster upgrades – when operators, incompatible with the next minor version of OpenShift, are installed on a cluster

This task enables the first bullet point above.

Why can't this wait until 4.9 is released?

Users relying on the opm binary in the release payload in 4.8.z won't be able to build custom catalog content using this feature.

Acceptance Criteria:

• bundles that contain CSV's with non-label type properties can be added to indexes
• non-label properties are visible in the listBundles gRPC API