[+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, <krmaya...@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-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/99c8fc8c-ff2e-499c-af68-3ab21c62a1ad% > 40googlegroups.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 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.
