phantomjinx opened a new issue #3017: URL: https://github.com/apache/camel-k/issues/3017
The OLM documentation has [recommendations](https://olm.operatorframework.io/docs/best-practices/channel-naming/) for naming of metadata bundle channels. Currently, camel-k uses a single version-named channel, eg. [stable-1.8.0](https://github.com/k8s-operatorhub/community-operators/blob/main/operators/camel-k/camel-k.package.yaml#L11). This requires users to change channel explicitly in order to upgrade. OLM best practices recommend the following alternative approach: - 3 channels of the form: candidate, fast (or latest) and stable where bundles would be published according to how production-ready and tested they might be. This would allow for unsupported snapshot bundles to be created for the `candidate` channel while only fully-tested releases would be available on `stable`. The `latest` channel would become the default channel where new releases are published with those releases only being added to the `stable` channel at a point when they have been sufficiently available. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
