anchor.diff:  
   |`*memory.available*`
   |`memory.available` = `node.status.capacity[memory]` - `node.stats.memory.workingSet`
  -|===
  +
  +|`*nodefs.available*`
  +|`nodefs.available` = `node.stats.fs.available`
  +
  +|`*nodefs.inodesFree*`
  +|`nodefs.inodesFree` = `node.stats.fs.inodesFree`
  +
  +|`*imagefs.available*`
  +|`imagefs.available` = `node.stats.runtime.imagefs.available`
  +
  +|`*imagefs.inodesFree*`
  +|`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 future releases, the node will support the ability to trigger eviction
  -decisions based on disk pressure. Until then, use
  +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].
  +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]]
  
positive.code: |`*MemoryPressure*`
  |`*memory.available*`
  |Available memory on the node has satisfied an eviction threshold.
  |===
  
  When the above is set the node continues to report node status updates at the
  frequency specified by the `node-status-update-frequency` argument, which
  defaults to *10s*.
  
  [[out-of-resource-eviction-of-pods]]
  === Eviction of Pods
  
negative.code: |Node Condition |Scheduler Behavior
  
  |`*MemoryPressure*`
  |If a node reports this condition, the scheduler will not place `BestEffort` pods on that node.
  
  |`*DiskPressure*`
  |If a node reports this condition, the scheduler will not place any additional pods on that node.
  |===
  
  [[out-of-resource-schedulable-resources-and-eviction-policies]]
  === Example Scenario
  