anchor.diff:  $ oc adm taint nodes node1 key2=value2:NoSchedule
   ----
   
  -* The pod has the following tolerations:
  +* The Pod has the following tolerations:
   +
   [source, yaml]
   ----
  
positive.code: // Module included in the following assemblies:
  //
  // * nodes/nodes-scheduler-taints-tolerations.adoc
  
  [id="nodes-scheduler-taints-tolerations-about_{context}"]
  = Understanding taints and tolerations
  
  A _taint_ allows a node to refuse pod to be scheduled unless that pod has a matching _toleration_.
  
  You apply taints to a node through the node specification (`NodeSpec`) and apply tolerations to a pod through the pod specification (`PodSpec`). A taint on a node instructs the node to repel all pods that do not tolerate the taint.
  
  Taints and tolerations consist of a key, value, and effect. An operator allows you to leave one of these parameters empty.
  
  
negative.code:       tolerationSeconds: 300
  ----
  
  These tolerations ensure that the default Pod behavior is to remain bound for 5 minutes after one of these node conditions problems is detected. 
  
  You can configure these tolerations as needed. For example, if you have an application with a lot of local state you might want to keep the Pods bound to node for a longer time in the event of network partition, allowing for the partition to recover and avoiding Pod eviction. 
  
  DaemonSet Pods are created with NoExecute tolerations for the following taints with no tolerationSeconds:
  
  * `node.kubernetes.io/unreachable`
  * `node.kubernetes.io/not-ready`
  
  This ensures that DaemonSet Pods are never evicted due to these node conditions, even if the `DefaultTolerationSeconds` admission controller is disabled.
  