The symptom you described suggests that multiple controller managers consider themselves to be leaders so they all try to create the pod (this does not have anything to do with the scheduler, which only assigns pods to nodes, it does not create pods). Specifically, if you followed the instructions here http://kubernetes.io/docs/admin/high-availability/#master-elected-components this shouldn't be happening.
On Sun, Nov 27, 2016 at 11:44 AM, 'mrpanigale' via Kubernetes user discussion and Q&A <[email protected]> wrote: > Yes I followed this guide as well as the coreos guide, specifically the > leader elect flag which presumably solves this problem. > > -- > 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. > -- 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.
