fix: remove operatorhub crd manifest #1177
Conversation
Remove the OperatorHub CRD manifest. Its existence causes the CRD to be applied during cluster bootstrapping -- as a part of the cluster-config-operator -- despite attempts to disable the marketplace component. The manifest will be relocated to the [marketplace-operator](https://github.com/operator-framework/operator-marketplace/). Signed-off-by: Nick Hale <njohnhale@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: njhale The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@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. |
|
/hold We're considering renaming the file instead of dropping it entirely. |
openshift-ci
bot
added
the
do-not-merge/hold
Superseded by #1178 |
1 participant
Superseded by #1178
Remove the OperatorHub CRD manifest. Its existence causes
the CRD to be applied during cluster bootstrapping -- as a
part of the cluster-config-operator -- despite attempts to
disable the marketplace component.
The manifest will be relocated to the marketplace-operator (see operator-framework/operator-marketplace#466).
Signed-off-by: Nick Hale njohnhale@gmail.com
Related:
cc @bparees @wking @perdasilva