You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using cluster_mode emulated it makes sense to set the --cluster_announce_ip (maybe in native mode as well?).
I would like to see this supported in the operator. It might break client libraries to not have this set up for e.g. the java library lettuce (see: redis/lettuce#1736).
I assume it should be easy to set up from within the operator using POD_IP references?
The text was updated successfully, but these errors were encountered:
For your specific usecase, Why can't you pass the --cluster_announce_ip arguement directly from the args field in the Dragonfly CR? We dont have plans to support cluster mode in Dragonfly Operator in the near future.
For setting a cluster announce ip i would need to know this ip, however it would be the ip of the service that the dragonfly operator creates. So it is unknown prior creation of the CR
When using cluster_mode emulated it makes sense to set the
--cluster_announce_ip
(maybe in native mode as well?).I would like to see this supported in the operator. It might break client libraries to not have this set up for e.g. the java library lettuce (see: redis/lettuce#1736).
I assume it should be easy to set up from within the operator using POD_IP references?
The text was updated successfully, but these errors were encountered: