[moving kubernetes-dev back to bcc]
On Sun, Feb 12, 2017 at 1:11 AM, <krmaya...@gmail.com> wrote: > Hi David > Thanks. You mean both nodeSelector and node affinity right. As per this > doc https://kubernetes.io/docs/admin/daemons/#running- > pods-on-only-some-nodes, both nodeSelector and node affinity work. > I believe that documentation is wrong. More specifically, the spec.template.spec.nodeSelector part is correct, but the .spec.template.metadata.annotations part is wrong (not yet supported for DaemonSet). The predicate functions respected by DaemonSet are only the ones listed here: https://github.com/kubernetes/kubernetes/blob/4ed86f5d4649ff9e612ad945b38ce9db147daaef/plugin/pkg/scheduler/algorithm/predicates/predicates.go#L840 > > But yeah my questions was about pod affinity/anti affinity which you are > saying doesnt work with DS. I am guessing it doesn't even make sense to > have pod affinity/anti affinity work with Daemon Sets since then daemon set > making a pod of certain kind per node definition would no longer be true ? > I guess you could use pod anti-affinity to say something like "one daemon per rack" but I agree that in general the uses are very limited. > > -Mayank > > > On Sunday, February 12, 2017 at 12:43:12 AM UTC-8, David Oppenheimer wrote: >> >> [+kubernetes-users; kubernetes-dev to bcc] >> >> No, and actually affinity doesn't work with DaemonSet right now either. >> The problem is that DaemonSet does its own scheduling and doesn't yet share >> all of the scheduler code. >> >> The only affinity-related constraint that works with DaemonSet right now >> is nodeSelector (a field of podSpec). >> >> >> On Sun, Feb 12, 2017 at 12:26 AM, <krma...@gmail.com> wrote: >> >>> After the node have been selected using node affinity, can you still use >>> pod affinity/anti affinity to further restrict daemon set pod placement ? >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Kubernetes developer/contributor discussion" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to kubernetes-de...@googlegroups.com. >>> To post to this group, send email to kuberne...@googlegroups.com. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/kubernetes-dev/99c8fc8c-ff2e-499c-af68-3ab21c62a1ad%40go >>> oglegroups.com >>> <https://groups.google.com/d/msgid/kubernetes-dev/99c8fc8c-ff2e-499c-af68-3ab21c62a1ad%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Kubernetes developer/contributor discussion" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-dev+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/kubernetes-dev/72b0b4ca-b6cc-40a6-b61a-5b0582d896a4% > 40googlegroups.com > <https://groups.google.com/d/msgid/kubernetes-dev/72b0b4ca-b6cc-40a6-b61a-5b0582d896a4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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.
