You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd gladly accept a PR for a redishappy+haproxy docker image ;-)
I've often thought to re-implement redishappy as a kubernetes operator but I think that would be a different project. Maybe redishappy's prime use case is to shore up legacy installations of redis?
This project interests me because I think that clients should not have to change the way they communicate with redis once you implement HA or cluster. Even if you want to optimize by serving reads from the slaves, an intermediary layer should control routing and load balancing of the reads without any configuration at the client end. Of course this is beyond the scope of this project as that would involve going beyond the network layer.
For the docker image, I was thinking independently of any orchestration or service discovery tool. I think a basic image should be created which can then be used with any other platform and with any existing redis setup. I don't think this should be difficult given that all the dependencies etc are already figured out in the vagrantfile. Let me see what I can do. :)
Hi, not really an issue.
Any plans to bundle redishappy+haproxy into a docker image which can be deployed on kubernetes (or other platforms)?
The text was updated successfully, but these errors were encountered: