If you specify the resources you need on your pods, we'll figure out where to put them. No need for node labelling in the general case.
On Fri, May 27, 2016 at 12:30 AM, Mark White <[email protected]> wrote: > Hi, > > Just a quick bit of feedback on the GKE node pools feature - it seems it > would be very useful to apply custom labels with the pools so you could have > a ‘high-cpu’ label on one pool, and a ‘high-mem’ label on another pool (for > example), then target the containers based on the labels. If you added a > third pool that was also high cpu you could tag it with the same label, > which isn’t possible with the existing 'cloud.google.com/gke-nodepool=' > label selector where each pool has a different label. > > > Thanks, > > Mark White > > Codec > > CTO > > (07400) 958883 > > -- > You received this message because you are subscribed to the Google Groups > "Containers at Google" 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/google-containers. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Containers at Google" 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/google-containers. For more options, visit https://groups.google.com/d/optout.
