Bug 2082763: Drop the OperatorHub CR instance#245
Conversation
|
Skipping CI for Draft Pull Request. |
|
/hold cancel The PR this was blocked on has merged. |
|
Approach looks good and the vendor changes came through well. /lgtm |
|
I support the changes here, but we will need to ask QE to update the OpenShift documentation which states that it ships with an operatorhub resource named cluster. Instead, we'll need this section to ask that the user manually create the resource. I was a bit worried that Marketplace won't behave as expected if the default operatorhub resource is not present, but this code indicates that the default catalogSources would be created as expected. I don't have approval permissions in this repo, but I'll give my support! |
The operatorhub CRD is now included in marketplace as part of it's CVO manifests; i.e. it's all or nothing anyway. |
Ah I did not know that the cluster operatorhub CR was moved to the Marketplace repo, sgtm. |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/hold I believe this is blocked on operator-framework/operator-marketplace#472 TL;DR, It seems like we're depending on an old version of openshift/api in marketplace, which means that the CRD manifest is old and is hitting some relatively new logic in CVO that prevents manifests w/o annotations from being merged. I suspect that bumping and revendoring openshift/api in marketplace will resolve this issue. |
|
/retest-required |
|
/hold cancel |
|
/lgtm |
|
@njhale: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/retitle Bug 2082763: Drop the OperatorHub CR instance |
|
@njhale: This pull request references Bugzilla bug 2082763, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Hi, I couldn't test it before merging via the |
you can produce a payload from this PR using cluster-bot, and then do your own install w/ the None capset, right? |
|
@kevinrizza Hey guys, what's missing for this to get merged? Manual testing by Jian? Could I ask that we please make this a priority. It would be great if we could get in asap, before Friday. Is there anything we can do to help expedite it? |
|
/approve |
|
holding it until qe finishes their testing, feel free to cancel the hold once qe is happy /hold |
|
@jianzhangbjz are you able to test this by using cluster-bot to build a payload from this PR, and then install from that payload w/ the None capset? |
|
@bparees Hi, I'm PTO yesterday, will try it today, thanks! |
|
LGTM based on https://bugzilla.redhat.com/show_bug.cgi?id=2082763#c5 |
|
/unhold |
|
@tkashem Could you help |
|
@njhale: All pull requests linked via external trackers have merged: Bugzilla bug 2082763 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene, bparees, exdx, jianzhangbjz, njhale, tkashem, tylerslaton The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Bump and vendor openshift/api to include a renaming of the OperatorHub(openshift/api was bumped in another PR)CRD yaml. This will preclude the CRD from cluster-config-operator's
CVO manifests and is part of an effort to make the marketplace-operator
optional via OpenShift's capabilities feature.