I guess my home work is to launch three API servers (assuming multiple API servers are not the problem) then launch one of either the controller or the scheduler to narrow down which component is not honoring the election result. [Election jokes omitted]
kind regards, Andrew On Monday, November 28, 2016 at 8:37:14 PM UTC+1, Daniel Smith wrote: > > I agree the symptom sounds like the components all consider themselves to > be the leader. > > On Sun, Nov 27, 2016 at 2:34 PM, 'mrpanigale' via Kubernetes user > discussion and Q&A <[email protected] <javascript:>> wrote: > >> An etcdctl cluster-health confirms on all nodes that the etcd cluster is >> healthy and all members are visible. The Masters are deployed using fleet >> so if there was a problem with etcd one of the Masters would not be running >> >> -- >> 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.
