(Special thanks to Avesh Agarwal from RedHat who did the PRs to make this
change.)


On Thu, Feb 23, 2017 at 2:13 PM, David Oppenheimer <david...@google.com>
wrote:

> FYI the PR that implemented this change for taints/tolerations (#38957)
> has merged, so if you build from HEAD you will get the new behavior.
>
> Thanks to everyone who helped with this, including the folks who own
> components that depend on this feature; it was a major effort.
>
>
> On Sun, Feb 19, 2017 at 2:27 PM, David Oppenheimer <david...@google.com>
> wrote:
>
>> I want to reiterate the announcement originally made here
>> <https://groups.google.com/d/msg/kubernetes-dev/-fwfHQtm9GE/H1TU4yqiBAAJ>
>> / here
>> <https://groups.google.com/d/msg/kubernetes-users/xf-VlRlAm2A/Th76aF-lAwAJ>:
>> *in Kubernetes 1.6, taints and tolerations will move from being
>> represented as annotations on Node and Pod, respectively, to being fields
>> of NodeSpec and PodSpec. The annotations will immediately stop having any
>> effect when you upgrade to 1.6*, as the annotation form is not supported
>> in 1.6.
>>
>> The PR for this (#38957) has not yet been merged but will be some time
>> this week (hopefully early in the week).
>>
>> Taints and tolerations are currently alpha and are not documented
>> (starting in 1.6 they will be beta), and are being used primarily by
>> Kubernetes system services today. So this shouldn't be a significant issue
>> for most users and developers. But *if you own a component that uses
>> taints and/or tolerations, you need to take action before the 1.6 code
>> freeze* (see the linked emails for more details)*. *
>>
>> We are doing the same thing for the "multiple scheduler" annotation as
>> well; see the linked emails for more details. Node and pod affinity, in
>> contrast to taints/tolerations and multiple scheduler, will continue to be
>> supported in their annotation form in 1.6, but will be removed in some
>> future release, so please shift to moving the beta (field) version of this
>> as soon as you can.
>>
>>
>

-- 
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... 'David Oppenheimer' via Kubernetes user discussion and Q&A
    • [kuber... 'David Oppenheimer' via Kubernetes user discussion and Q&A
      • [k... 'David Oppenheimer' via Kubernetes user discussion and Q&A

Reply via email to