Yeah, unfortunately you'll have to write a custom operator or scheduler until local PVs are available. Another option is to consider running as a DaemonSet, then you will only have one pod per node and won't need a custom scheduler.
On Mon, May 8, 2017 at 12:33 AM, vincent gromakowski < vincent.gromakow...@gmail.com> wrote: > I was thinking of using pod to pod anti affinity and pod to node affinity > to stick pod to nodes depending on local volumes. Should I write a custom > scheduler to map pod to disks and then stick to nodes? > > -- > 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.
