publish on operatorhub

[ibotty]

It would be great to have a working operator on OperatorHub for non redhat customers.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[ibotty]

still relevant.
/remove-lifecycle stale

[ibotty]

/remove-lifecycle stale

[ibotty]

/lifecycle frozen

[ibotty]

Anything one can do to move that issue forward?

[ibotty]

I published the 4.11-Release using the following catalogsource: https://gitlab.com/ibotty/okd-operators/-/raw/main/okd-operators.catalogsource.yaml?inline=false

It uses the images quay.io/openshift/origin-local-storage-operator:4.11 and quay.io/openshift/origin-local-storage-diskmaker:4.11.

[lfarkas]

IMHO it's a very basic operator without OKD not really useful. So would anybody who is responsible for this project write the official statement of redhat? What is the reason that this (and many other) very basic operator not published on operatorhub? this is a force that no one really try to use OKD in any kind of production environment?