anchor.diff:  * Valid `operator` tokens are `<`.
   * Valid `quantity` tokens must match the link:https://github.com/kubernetes/kubernetes/blob/master/docs/design/resources.md#resource-quantities[quantity representation] used by
   Kubernetes.
  -
  -For example, using the `memory.available` signal, in order to construct a
  -threshold for when the memory available drops below 500Mi, the form would be:
  -
  -----
  -memory.available<500Mi
  -----
  -
  +* an eviction threshold can be expressed as a percentage if it ends with the `%` token.
  +
  +For example, if an operator has a node with 10Gi of memory, and that operator
  +wants to induce eviction if available memory falls below 1Gi, an eviction
  +threshold for memory can be specified as either of the following:
  +
  +---
  +memory.available<1Gi
  +memory.available<10%
  +---
   
   [[out-of-resource-soft-eviction-thresholds]]
   ==== Soft 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: 
  |`*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 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]]
  