anchor.diff:  == Tolerating all taints
   
   You can configure a pod to tolerate all taints by adding an `operator: "Exists"` toleration with no `key` and `value` parameters.
  -Pods with this toleration are not removed from a node that has taints. 
  +Pods with this toleration are not removed from a node that has taints.
   
   .`Pod` spec for tolerating all taints
   [source,yaml]
  
positive.code: The Taint-Based Evictions feature, which is enabled by default, evicts pods from a node that experiences specific conditions, such as `not-ready` and `unreachable`.
  When a node experiences one of these conditions, {product-title} automatically adds taints to the node, and starts evicting and rescheduling the pods on different nodes.
  
  Taint Based Evictions have a `NoExecute` effect, where any pod that does not tolerate the taint is evicted immediately and any pod that does tolerate the taint will never be evicted, unless the pod uses the `tolerationsSeconds` parameter.
  
  The `tolerationSeconds` parameter allows you to specify how long a pod stays bound to a node that has a node condition. If the condition still exists after the `tolerationSections` period, the taint remains on the node and the pods with a matching toleration are evicted. If the condition clears before the `tolerationSeconds` period, pods with matching tolerations are not removed.
  
  If you use the `tolerationSeconds` parameter with no value, pods are never evicted because of the not ready and unreachable node conditions. 
  
  [NOTE]
  ====
  
negative.code:       tolerations:
        - operator: "Exists"
  ----
  