Open diptripa opened 1 year ago
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. I would fix this asap. Putting this in the next milestone
During concile patch role label of pods
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?
Created redis-replication using this manifest:
Changed some parameters like storage requests and cpu, memory requests.
Connected to service redis-replication:6379 from app.
What did you expect to see? That it is serving the cache without any issues.
What did you see instead?