Redis cluster setup with chripstick with R/W separation

In terms of Redis cluster deployed on kubernetes cluster (not a a managed service) plus chripstick integration
we need to separate the read from write traffic
what is the best way to achieve Highly setup for this ?
the problem is that we can’t set endpoint for dedicate for each operation. i.e, we can’t say that X endpoint is for read and Y is for write operation, However if we try to dedicate master node for write, the request sometime redirected to be served from the other slaves

Can you create Redis users with different permissions? For example, a read user with read only permissions and a write user with read & write permissions.

This topic was automatically closed after 90 days. New replies are no longer allowed.