-
-
Notifications
You must be signed in to change notification settings - Fork 233
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
Redis Replication service pointing to read-only replica #629
Comments
Same issue here. It would appear the there is no separate service created that targets the master specifically. It also appears this may be the intentional design and we have to use the sentinel setup to act as a proxy layer for this? |
We have the same issue. A possible solution would be to use some kind of sidecar next to the redis replication containers to change the labels or have the operator do this. |
Same issue here |
Same issue. Is there any solution? |
Didn't get time for this. |
During concile patch role label of pods |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
We are having this issue. |
What version of redis operator are you using?
redis-operator version: 0.15
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
What did you expect to see?
That it is serving the cache without any issues.
What did you see instead?
The text was updated successfully, but these errors were encountered: