Are you open to cooperation?

[gdubicki]

Hi!

Big thank you for taking over the development of spotahome/redis-operator after it got unmaintained! 😊🙏

After I did some research, your fork came out as the most developed, so I have tried to start using it instead of the origin.

However I had to do some very basic changes and updates to do this, and it made me think that perhaps you don't want others to use it, if you haven't made those changes yourselves?

What I mean is that while I obviously don't expect you to give any guarantees, support, etc. for this code, would you be willing to:

• talk about using this operator, in particular regarding the features you have added, like HAproxy?
• look into reported issues, as they may be something you have already encountered yourselves and have workarounds or that you will encounter?
• review and merge PRs with improvements?

Sorry if these questions seem stupid, as because this repo is public, it should mean that the answer is "yes" to all of them, but the lack of issues and PRs from people from outside of Power Home makes me have this doubt, if it's worth investing in it.

Cheers!

[gdubicki]

Hey @indiebrain, perhaps you can reply here, please? 🙏😊

[Nklya]

I would say this fork is quite active as well https://github.com/freshworks/redis-operator

[gdubicki]

I would say this fork is quite active as well https://github.com/freshworks/redis-operator

Yes, I noticed it too, but I encountered this issue while I tried to use that fork, @Nklya: freshworks#37

[gdubicki]

Hey @rurkss, maybe you could take a look at this, please?

[indiebrain]

@gdubicki, thanks for your interest. This fork was made under the Apache 2 license. Contributions are welcomed, but - as with any opensource project - not guaranteed incorporation in the mainstream trunk. You are also free to fork this fork if you so desire or need.

Apologies for the delayed response. I've added reviewing your PR to my TODO list.

EDIT:

Clicked the submit button before I addressed all the original questions. Again, apologies.

talk about using this operator, in particular regarding the features you have added, like HAproxy?

We actively use this operator in prodcution. HAProxy is an optional component which comes with its own complexity, but it does detect failovers and redirect client traffic more quickly than an operator tick - in our experience less than 1 second. In practice it's ok, but the additional complexity should be considered. We've run into issues with this bespoke topology and our attempts to implement it before. Fore example:

• haproxy: disconnect clients when node is demoted to replica #59

I'm happy to answer any other specific questions you have.

look into reported issues, as they may be something you have already encountered yourselves and have workarounds or that you will encounter?

Examples of specific "reported issues" would be helpful, but again we're open to addressing concerns that would make this operator more widely usable.

review and merge PRs with improvements?

Absolutely.