Adding a NoSchedule taint to a node should not cause any pod evictions. Something else must be going on.
On Fri, Oct 6, 2017 at 3:03 PM, Budai Laszlo <laszlo.bu...@gmail.com> wrote: > Dear All, > > I have a question related to Taints > I'm testing taints on a K8s 1.6.3 cluster with weave-net network plug-in, > and the kube-proxy deployed as a DaemonSets. > > When I'm adding a taint like mykey:myvalue:NoSchedule to a node I see that > the weave-net pod, and the kube-proxy pod are deleted from that node. > > Why is that happening? > > According to the documentation the `NoSchedule` effect should leave > untouched the pods that are already running on a node, and I can see that > other pods remain there (for example the kube-dns, or a test pod created by > me). > > Thank you in advance for any suggestion. > > Kind regards, > Laszlo > > -- > 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. > -- 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.
