Hi Rodrigo.
If you look at the redis-master.yaml, there's a pod with the following labels:
metadata:
labels:
name: redis
redis-sentinel: "true"
role: master
redis-controller.yaml describes a replication controller with selector:
metadata:
name: redis
spec:
replicas: 1
selector:
name: redis
redis-sentinel-controller.yaml describes a replication controller with
selector:
metadata:
name: redis-sentinel
spec:
replicas: 1
selector:
redis-sentinel: "true"
Both replication controller selectors will match the first POD labels. Unless
I'm misunderstanding something, here we have two replication controllers
fighting for the same pod. This "arrangement" is convenient for setting up a
redis cluster, because initially we have to set one redis instance as master
explicitly. After that the cluster will take care of electing a new master if
necessary.
Thanks,
Rui
--
You received this message because you are subscribed to the Google Groups
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.
