Hi,
The version on operatorhub (1.3.0) is quite outdated, is it possible to update it there as well?
Thx,
Patrick
Last time I wanted to update the operator there it failed the scorecard because of a new rule the authors implemented. Deploying our operator via OLM is not as user friendly as compared to kustomize or helm. So, changing great parts of our code base only to pass tests there is def. not worth the effort. Have you tried operatorhub and liked the experience?
I dont have a need for operator hub, but if it is offered (both on operatorhub and quickstart.md), it should be up to date. If supporting operator hub is too much affort, I suggest delisting it there and removing the reference from documentation to avoid problems if the prepared setup is not supported anymore.
I asked where to find the roles, maybe we can reassess. Would not like to not be present there :D
@FxKu It looks like they removed the scorecard tests that were blocking the 1.4.0 release:
https://github.com/operator-framework/community-operators/pull/1281#issuecomment-693583373
@FxKu I reran your PR, and it seems to pass the CI now:
https://github.com/operator-framework/community-operators/pull/2929
If you can talk me through what would be needed for the 1.5.0 and 1.6.0 releases to get them on operatorhub, I would be willing to take the time to do the work!
@FxKu The 1.4.0 release has been merged in, and is now available on OperatorHub.io. I would still like to get the 1.5.0 and 1.6.0 releases available there though.
Most helpful comment
I asked where to find the roles, maybe we can reassess. Would not like to not be present there :D