A new OpenShift operator community testing workflow release #3679
Replies: 3 comments
-
mentions: |
Beta Was this translation helpful? Give feedback.
-
Hey community, There are a couple of open PRs at this moment with new operators. We will switch them into the draft at this moment and continue after the release. Thanks for understanding, |
Beta Was this translation helpful? Give feedback.
-
The new version of the community operator pipeline has been released! The first bundle passed the tests and has been successfully release. We are going to review current PRs and make sure they are processed as well. Please let us know if you see any unexpected behavior! Thank you. |
Beta Was this translation helpful? Give feedback.
-
Dear OpenShift Operator Community,
We would like to announce a plan for the new OpenShift operator community testing workflow release. The current workflow as you know it will transition to a workflow that you might know from OpenShift Certified and Marketplace operators. With this step, we want to unify the interface for submitting OpenShift operators from various sources.
With the new workflow, we want to keep most of the functionality from the old pipeline and support it into a new workflow. However, due to performance and reliability issues we have been facing we introduce a couple of changes:
Installation Testing: Our testing protocols will shift to focus on the latest supported version defined by the operator. This ensures that our evaluations align with the most current and relevant standards.
Single Operator Bundle: With the new workflow, each Github pull request will now accommodate only one operator bundle. This adjustment aims to streamline the review and integration process for better efficiency.
IIB Integration: Introducing the use of IIB (Index Image Builder) for constructing index images. This change promises increased efficiency and consistency in our image building processes. The IIB service has no impact on the bundle submission format and operator owner input remains the same.
Bundle Removal Restriction: Removal or update of a bundle is no longer allowed. This restriction ensures that operator users won't end up with a broken operator in case an operator is removed from an index.
We are aiming for these changes to be released in a week starting from 18th of December.
FBC Support (File-Based Catalog): While the FBC is not part of this release, it's on the horizon. This release will move us closer to implementing FBC, providing you with a more efficient and customizable way to manage your operator.
We appreciate your understanding and adaptability during this transition. These updates are designed to foster collaboration, improve efficiency, and ensure our workflows remain robust and effective.
Thank you for your continued support.
Beta Was this translation helpful? Give feedback.
All reactions