anchor.diff:  [id="nodes-scheduler-taints-tolerations-about-seconds_{context}"]
   == Understanding how to use toleration seconds to delay pod evictions
   
  -You can specify how long a pod can remain bound to a node before being evicted by specifying the `tolerationSeconds` parameter in the pod specification. If a taint with the `NoExecute` effect is added to a node, any pods that do not tolerate the taint are evicted immediately (pods that do tolerate the taint are not evicted). However, if a pod that to be evicted has the `tolerationSeconds` parameter, the pod is not evicted until that time period expires.
  +You can specify how long a Pod can remain bound to a node before being evicted by specifying the `tolerationSeconds` parameter in the Pod specification. If a taint with the `NoExecute` effect is added to a node, any Pods that do not tolerate the taint are evicted immediately (Pods that do tolerate the taint are not evicted). However, if a Pod that to be evicted has the `tolerationSeconds` parameter, the Pod is not evicted until that time period expires.
   
   For example:
   [source, yaml]
  
positive.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.
  
negative.code: 
  * `node.kubernetes.io/not-ready`: The node is not ready. This corresponds to the node condition `Ready=False`.
  * `node.kubernetes.io/unreachable`: The node is unreachable from the node controller. This corresponds to the node condition `Ready=Unknown`.
  * `node.kubernetes.io/out-of-disk`: The node has insufficient free space on the node for adding new Pods. This corresponds to the node condition `OutOfDisk=True`.
  * `node.kubernetes.io/memory-pressure`: The node has memory pressure issues. This corresponds to the node condition `MemoryPressure=True`.
  * `node.kubernetes.io/disk-pressure`: The node has disk pressure issues. This corresponds to the node condition `DiskPressure=True`.
  * `node.kubernetes.io/network-unavailable`: The node network is unavailable.
  