Abhishek Gupta

so is there any way that i can run redis -cluster having following conditions 1) cluster type = minikube (does not have external ip support) 2) external.access =true ( I...

i tried using the approach you suggested but now i am unable to create cluster only . Also when i try to connect to pods using external ip and port...

Also what is the reason to make it mandatory to create loadbalancer services in this chart . we could have made any pod acessible from outside using nodeport and rest...

if we want that client should be able to connect to each of the pods , then we can simply have nodeports for each pod and the client can connect...

i am still unable to understand why use external ip when we can do same thing by just providing different nodeports to different pods . if we want to connect...

Also if we do not want -c parameter , the client can connect to any pod if he knows correct master ip where hast slot i served

if we leave the problem of external ip , i should be able to connect to 192.168.49.2:30106 atleast . but i am unable to connect to it. is it due...

As you mentioned that redis should have both internal ip and external ip same . then can we run using these approaches - 1) use nodeports for every pod and...

So is there a way that like in redis-sentinel we can announce ip into hostnames , we can do here in redis-cluster also . it will make external access easier...

Also as you said that redis publish same ip for both internal and external communication. i have deployed a helm chart with redis-sentinel architecture and when i see sentinel masters...