search

bitpoke / mysql-operator

Asynchronous MySQL Replication on Kubernetes using Percona Server and Openark's Orchestrator.
https://www.bitpoke.io/docs/mysql-operator/getting-started/
Apache License 2.0
1.04k stars 275 forks source link

Register MySQL Operator into OperatorHub.io #244

Open AMecea opened 5 years ago

AMecea commented 5 years ago

https://www.operatorhub.io/contribute

AMecea commented 5 years ago

Depends on #259 and https://github.com/operator-framework/operator-lifecycle-manager/issues/767 .

komish commented 4 years ago

Hi @AMecea!

I understand that Orchestrator is a stateful component and is primarily the motivation behind making use of the statefulset as the operator deployment methology. Could you give some examples of which statefulset behaviors are key for Orchestrator? Is it possible to decouple the Operator from the Orchestrator and have them communicate through some other method or do they need to live in the same pod?

Not super familiar with Orchestrator here, but I am trying to get more information on the statefulset use case here and see if there's a way we can approach it that might resolve the dependency on https://github.com/operator-framework/operator-lifecycle-manager/issues/767 in the meantime.