Stop requiring channel information within bundle image metadata.

[anik120]

Currently, the annotations.yaml file in a bundle requires operators.operatorframework.io.bundle.channels.v1, while operators.operatorframework.io.bundle.channel.default.v1 is optional. With the introduction of the olm.channel schema for plain-text storage backed Catalogs, the channel information must no longer be included in the bundle by operator authors. Instead, that information should be included/edited in the plain-text files that make up the Catalog.

While building a Catalog using the plaintext files, if the operators.operatorframework.io.bundle.channels.v1 field is omitted, the following error is thrown:

$ opm render docker.io/anik120/etcd:sha-2b68f58
2021/09/15 11:19:51 render reference "docker.io/anik120/etcd:sha-2b68f58": Could not find annotations file

The operators.operatorframework.io.bundle.channels.v1 field should no longer be allowed inside the bundle.

Caveat to consider:
That field is still required for sqllite backed Catalogs. Since the bundle building process is agnostic to what storage is used in the Catalog it is being included in, there needs to be a middle ground for the time being while sqllite backed Catalogs are still deprecated, so that the field serves the sqllite backed Catalogs, while also not coming in the way of plaintext files backed Catalogs.

[anik120]

Also, the opm alpha bundle --generate still creates an annotations.yaml that has the channel information in it. This should be modified too to communicate what is expected in the bundle. Same caveat to consider as above.

[github-actions]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

[github-actions]

This issue has been closed due to inactivity.