anchor.diff:  defaults to *10s*.
   
   [[out-of-resource-reclaiming-node-level-resources]]
  -=== Reclaiming node level resources
  -
  -If an eviction criteria have been satisfied, the node
  -will initiate the process of reclaiming the pressured resource until it has
  -observed the signal has gone below its defined threshold.  During this time,
  -the node does not support scheduling any new pods.
  -
  -The node attempts to reclaim node level resources prior to evicting end-user pods.
  -If disk pressure is observed, the node reclaims node level resources differently
  -if the machine has a dedicated `imagefs` configured for the container runtime.
  -
  +=== Reclaiming Node-level Resources
  +
  +If an eviction criteria is satisfied, the node initiates the process of
  +reclaiming the pressured resource until it observes that the signal has gone
  +below its defined threshold. During this time, the node does not support
  +scheduling any new pods.
  +
  +The node attempts to reclaim node-level resources prior to evicting end-user
  +pods. If disk pressure is observed, the node reclaims node-level resources
  +differently if the machine has a dedicated `imagefs` configured for the
  +container runtime.
  +
  +[[reclaiming-with-imagefs]]
   ==== With Imagefs
   
  -If `nodefs` filesystem has met eviction thresholds, the node will free up disk space in the following order:
  +If the `nodefs` file system meets eviction thresholds, the node frees up disk
  +space in the following order:
   
   * Delete dead pods/containers
   
  -If `imagefs` filesystem has met eviction thresholds, the node will free up disk space in the following order:
  +If the `imagefs` file system meets eviction thresholds, the node frees up disk
  +space in the following order:
   
   * Delete all unused images
   
  +[[reclaiming-without-imagefs]]
   ==== Without Imagefs
   
  -If `nodefs` filesystem has met eviction thresholds, the node will free up disk space in the following order:
  +If the `nodefs` file system meets eviction thresholds, the node frees up disk
  +space in the following order:
   
   * Delete dead pods/containers
   * Delete all unused images
  
positive.code: |Available memory on the node has satisfied an eviction threshold.
  
  |`*DiskPressure*`
  |`*nodefs.available*`, `*nodefs.inodesFree*`, `*imagefs.available*`, or `*imagefs.inodesFree* 
  |Available disk space and inodes on either the node’s root filesytem or image filesystem has satisfied an eviction threshold.
  |===
  
  When the above is set the node continues to report node status updates at the
  
negative.code: 
  As a result, if a pod is evicted as a consequence of consuming too much disk in
  an `EmptyDir` volume, the pod will be evicted, but the local volume usage will
  not be reclaimed by the node. The node will keep evicting pods on the node to
  prevent total exhaustion of disk. Operators can reclaim the disk by manually
  deleting the evicted pods from the node once terminated.
  
  This will be remedied in a future release.
  