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: 
  |`*memory.available*`
  |`memory.available` = `node.status.capacity[memory]` - `node.stats.memory.workingSet`
  |===
  
  [NOTE]
  ====
  In future releases, the node will support the ability to trigger eviction
  decisions based on disk pressure. Until then, use
  xref:../admin_guide/garbage_collection.adoc#admin-guide-garbage-collection[container
  and image garbage collection].
  ====
  
  [[out-of-resource-eviction-thresholds]]
  
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
  