anchor.diff:  the strategy targets the largest consumer of the starved resource.
   * `Guaranteed`: pods that consume the most of the starved resource relative to
   their request are failed first. If no pod has exceeded its request, the strategy
  -targets the largest consumer of the starved resource. 
  +targets the largest consumer of the starved resource.
   
   A `Guaranteed` pod will never be evicted because of another pod's resource
   consumption unless a system daemon (node, *docker*, *journald*, etc) is
  
positive.code: |`imagefs.inodesFree` = `node.stats.runtime.imagefs.inodesFree`
  |===
  
  The node supports two filesystem partitions when detecting disk pressure.
  
  * The `nodefs` filesystem that the node uses for local disk volumes, daemon logs, etc (i.e. the filesystem that provides `/`)
  * The `imagefs` filesystem that the container runtime uses for storing images and individual container writable layers.
  
  The node auto-discovers these filesystems using `cAdvisor`.
  
  If you store volumes and logs in a dedicated filesystem, the node will not monitor that filesystem at this time.
  
  [NOTE]
  ====
  In this release, the node supports the ability to trigger eviction decisions
  based on disk pressure.  Operators must opt-in to enable disk based evictions this
  release.  Prior to evicting pods due to disk pressure, the node will also perform
  container and image garbage collection.  For more detail on garbage collection, see
  xref:../admin_guide/garbage_collection.adoc#admin-guide-garbage-collection[container
  and image garbage collection].  In future releases, garbage collection will be deprecated
  in favor of a pure disk eviction based configuration.
  ====
  
  [[out-of-resource-eviction-thresholds]]
  
negative.code: stability and limits the impact of the unexpected consumption to other
  `Guaranteed` pods.
  
  Local disk is a `BestEffort` resource. If necessary, the node will evict pods
  one at a time to reclaim disk when `DiskPressure` is encountered. The node ranks
  pods by quality of service. If the node is responding to inode starvation, it
  will reclaim inodes by evicting pods with the lowest quality of service first.
  If the node is responding to lack of available disk, it will rank pods within a
  quality of service that consumes the largest amount of local disk, and evict
  those pods first.
  
  [NOTE]
  ====
  