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

Consider supporting redis sentinel #88

Open
SEJeff opened this issue Mar 11, 2020 · 2 comments
Open

Consider supporting redis sentinel #88

SEJeff opened this issue Mar 11, 2020 · 2 comments

Comments

@SEJeff
Copy link

@SEJeff SEJeff commented Mar 11, 2020

We run this scim bridge in kubernetes and would like to use a highly available redis instance. The k8s redis-operator makes this trivial, but to use it properly, the application needs to be sentinel aware. This allows having a master redis and 2 read-only slaves ensuring uninterrupted availability when a node gets evicted due to hardware problems or whatnot.

@cohix

This comment has been minimized.

Copy link
Contributor

@cohix cohix commented Mar 11, 2020

Thanks for the feedback :) I rarely hear of anyone running redis sentinel in production, so this is the first request I've heard for it.

@SEJeff

This comment has been minimized.

Copy link
Author

@SEJeff SEJeff commented Mar 11, 2020

It is the most sensible way to reliably run HA redis in kuberntes. I'm sure there are plenty of other people using it as the default redis-operator config spins up three sentinel pods. It would be very much appreciated if the scim bridge we use for production (we're a paying customer) supported this!

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.