For now, we solved this by running a simple looped script on our cluster: while true; do kubectl taint nodes -l type=regular dedicated=regular:NoSchedule sleep 60 done
Make sure you create your GKE node-pool(s) with the right labels, and this will make sure they are tainted, even if new ones are started. On Monday, August 21, 2017 at 6:41:04 AM UTC+2, David Oppenheimer wrote: > Sorry, not implemented yet. It's definitely on our TODO list, so watch the > GKE release notes (or ping this thread periodically :-) > > > > > > > > > > On Fri, Aug 18, 2017 at 6:47 AM, <je...@blendle.com> wrote: > Just to make my feature request a bit more clear: > > > > I'd like to be able to taint node-pools, which we would use to taint the > node-pool that consists of regular nodes in our cluster, just as David > proposed. > > > > > > On Friday, August 18, 2017 at 3:46:01 PM UTC+2, je...@blendle.com wrote: > > > Has this feature been implemented already? If it has, I haven't been able > > to find it in the docs or the CLI man pages. > > > > > > We are looking for the exact opposite of this request: to taint regular > > nodes, so all deployments, except the ones that *require* a regular node, > > are automatically deployed to our preemptible nodes. > > > > > > On Monday, November 21, 2016 at 9:58:29 AM UTC+1, Micke Lisinge wrote: > > > > Thanks David! > > > > > > > > Den måndag 21 november 2016 kl. 09:54:39 UTC+1 skrev David Oppenheimer: > > > > Thanks for the suggestion. I think it's a reasonable suggestion and I've > > > filed an internal feature request to add this to gcloud, but I can't > > > guarantee if/when it will be implemented. > > > > > > > > > > > > On Mon, Nov 21, 2016 at 12:34 AM, Micke Lisinge <lis...@rabble.se> wrote: > > > > > > > > For sure, i'm not asking you to change the defaults. > > > > Exactly, if you could add a "--node-taints" flag, just like the > > > "--node-labels" flag works to "gcloud beta container node-pools create" > > > then it would cover my use case. > > > > > > > > Den måndag 21 november 2016 kl. 01:11:28 UTC+1 skrev David Oppenheimer: > > > > > > > > Nodes running on preemptible VMs are labeled with > > > cloud.google.com/gke-preemptible=true > > > > (see documentation here) > > > > > > > > > > > > The downside of using a taint instead (or in addition) is that then users > > > would have to explicitly add tolerations to use these nodes. So the > > > default out-of-the-box behavior would be more complicated (and, for > > > people who didn't thoroughly read the documentation, confusing). > > > > > > > > > > > > I guess we could add an option to "gcloud beta container node-pools > > > create" to tell GKE to add a taint in addition to a label, so users who > > > wanted this behavior could request it. > > > > > > > > > > > > > > > > > > > > On Wed, Nov 16, 2016 at 6:00 AM, Micke Lisinge <lis...@rabble.se> wrote: > > > > > > > > With the possibility of creating preemptible node pools on GKE it would > > > be amazing if you could also taint these nodes, maybe even enable setting > > > taints for all pools just like you can label pools today. > > > > I know taints are currently in alpha but it would be great if this could > > > get taken into consideration for when taints reaches beta. > > > > > > > > > > > > I know this could also be solved with node affinity and anti-affinity but > > > it would be amazing if you would be able to taint nodes to only be used > > > by pods with the proper toleration. > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > 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-use...@googlegroups.com. > > > > > > > > To post to this group, send email to kubernet...@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-use...@googlegroups.com. > > > > > > > > To post to this group, send email to kubernet...@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-use...@googlegroups.com. > > To post to this group, send email to kubernet...@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.