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 <lisi...@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
>> <https://cloud.google.com/container-engine/docs/preemptible-vm>)
>>
>> 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
>>> <https://github.com/kubernetes/kubernetes/blob/master/docs/design/taint-toleration-dedicated.md>,
>>> 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-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.
  • [kubernetes... Micke Lisinge
    • Re: [k... 'David Oppenheimer' via Kubernetes user discussion and Q&A
      • Re... Micke Lisinge
        • ... 'David Oppenheimer' via Kubernetes user discussion and Q&A
          • ... Micke Lisinge
            • ... jean
              • ... jean
                • ... 'David Oppenheimer' via Kubernetes user discussion and Q&A
                • ... jean
                • ... 'Ajit Kumar' via Kubernetes user discussion and Q&A
                • ... donina . lorenzo
                • ... 'David Oppenheimer' via Kubernetes user discussion and Q&A
                • ... Lorenzo Donina
                • ... 'David Oppenheimer' via Kubernetes user discussion and Q&A

Reply via email to