Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker Image #62

Open
stingerpk opened this issue Feb 7, 2017 · 2 comments
Open

Docker Image #62

stingerpk opened this issue Feb 7, 2017 · 2 comments

Comments

@stingerpk
Copy link

Hi, not really an issue.

Any plans to bundle redishappy+haproxy into a docker image which can be deployed on kubernetes (or other platforms)?

@mdevilliers
Copy link
Owner

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?

@stingerpk
Copy link
Author

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. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants