-
Notifications
You must be signed in to change notification settings - Fork 562
Update openshift-nfd-operator to latest changes #3402
Update openshift-nfd-operator to latest changes #3402
Conversation
Signed-off-by: Carlos Eduardo Arango Gutierrez <carangog@redhat.com>
Hi @ArangoGutierrez. Thanks for your PR. I'm waiting for a operator-framework member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/hold Only minor (cosmetic) changes to already published operator version(s) are allowed.
More info about allowed changes can be found in [documetnation](https://operator-framework.github.io/community-operators/troubleshooting/#minor-changes).
|
/hold cancel |
/hold |
/hold cancel |
/test all |
yay all green!!! @J0zi !!! |
@J0zi @mvalarh
This PR is needed to sync up this community operator with recent changes to the operator code base.
We removed the check for readiness probe, and users trying to install the operator from OperatorHub
community
operator edition, are hitting an error bc the container that get's pulled is from the updated version of the operator on the Downstream https://github.com/openshift/cluster-nfd-operator , without this change NFD community edition will be broken for future users .this is why this is not a simple cosmetic change to an existing release.
Signed-off-by: Carlos Eduardo Arango Gutierrez carangog@redhat.com
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions
Updates to existing Operators
ci.yaml
file according to the update instructions?replaces
property if you chosereplaces-mode
via theupdateGraph
property inci.yaml
?package.yaml
orannotations.yaml
?Your submission should not
upstream-community-operators
andcommunity-operators
at onceOperator Description must contain (in order)
Operator Metadata should contain
Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here