-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devfile registry operator pre-release to OperatorHub #1211
Comments
I think we should start with |
Add minimal documentation for publication to OperatorHub |
Documentation acceptance criteria has been included. |
Begun prep work for pre-release. Updated maintainers, CR descriptors, and set version fields to |
Waiting for devfile/registry-operator#45 to merge: #1106 (comment) |
Rebased prep changes with recent changes from devfile/registry-operator#45 & devfile/registry-operator#46 |
It seems that For this issue, I cannot generate the examples of Will try manually entering the examples of |
Part 1 of this issue is ready for review: devfile/registry-operator#47 |
Part 2: Cutting the new release |
New release
This part is being blocked by #1251 due to OLM validation passing being required for publication to OperatorHub. |
Contributing doc for OperatorHub: https://github.com/operator-framework/community-operators/blob/master/docs/contributing-via-pr.md |
Candidate for demo at the end of the Sprint in which it will be completed. |
Keeping status blocked to include #1028 under new release cut. |
New release v0.1.1 has been cut on GitHub.
Starting part 3 to publish to OperatorHub. |
Opened a PR with current version's bundle: Experiencing an failing check which seems to be flagging a missing field which is not missing from the CSV file: k8s-operatorhub/community-operators#3287 (comment) |
Opened Q&A discussion about this problem: k8s-operatorhub/community-operators#3294 |
Update: I received feedback on this problem and found that |
There is a missing place to update the operator version: k8s-operatorhub/community-operators#3287 (comment) Investigating this on the operator side. |
Opened PR for new patch changes: devfile/registry-operator#54 These changes will fully pass kiwi testing: https://github.com/k8s-operatorhub/community-operators/actions/runs/6487040924/job/17616540337 |
PR to publish to OperatorHub.io is now ready for review: k8s-operatorhub/community-operators#3287 |
Publication PR k8s-operatorhub/community-operators#3287 has now been merged and the registry operator is now published to OperatorHub.io: https://operatorhub.io/operator/registry-operator Closing this issue. |
Which area/kind this issue is related to?
/area registry
/area releng
Issue Description
In #410, we plan to make our first release of the registry operator available on OperatorHub for consumers. To ensure early adopters are ready to ship when this release becomes available, it would be necessary to also provide pre-releases.
Resolve #1106 to ensure no problems with publishing.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: