Add Scylla Operator to https://operatorhub.io/

[tzach]

https://operatorhub.io/ holds many open-source operators for user to use. It will be useful to add Scylla to this list once it is ready

A next step can be to certify the operator https://connect.redhat.com/explore/red-hat-openshift-operator-certification

[dyasny]

I don't think it was ever tested with openshift, openshift is based on k8s, but it also has some differences

[dahankzter]

Operatorhub seems "standard" so that we should do. As for Openshift I think we can count on the internals being kubernetes compatible or it would break so many functional operators and charts which would make Openshift dead in the water. It needs testing of course like @dyasny suggested and some tweaks here and there I am sure.

[dyasny]

@dahankzter openshift defaults to specific networkig configs we might not have tested (weave/flanel instead of calico for example) and it typically uses CRI-O instead of docker, and that's just the tip of the iceberg there :)

[dahankzter]

This is out of scope for 1.0 at least I think @tzach since it seems to be very Openshift oriented.

[mykaul]

Depends on https://github.com/scylladb/scylla-operator/issues/424

[scylla-operator-bot[bot]]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[tnozicka]

/remove-lifecycle stale /triage accepted