It seems exactly that, it might be that the etcd are not correctly in the same cluster. I'd review that first
On Sunday, November 27, 2016, 'mrpanigale' via Kubernetes user discussion and Q&A <[email protected]> wrote: > Absolutely agree with you that this should not be happening. Unfortunately > the documentation does not match up with the reality once utilizing the > leader elect flags on both the scheduler and the controller. > > Is there an etcd key within the registry hierarchy that displays the > leader ip? > > -- > 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 [email protected] <javascript:;>. > To post to this group, send email to [email protected] > <javascript:;>. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
