anchor.diff:        effect: NoSchedule
   ----
   
  -* Daemon sets can use labels to ensure that a workload runs on a matching worker node. 
  +* Daemon sets can use labels to ensure that a workload runs on a matching worker node.
   
  -* You can use an {product-title} service endpoint to load balance daemon set pods. 
  +* You can use an {product-title} service endpoint to load balance daemon set pods.
   
   [NOTE]
   ====
  -Daemon sets do not schedule pods after a reboot of the node if {product-title} cannot reach the node. 
  +Daemon sets do not schedule pods after a reboot of the node if {product-title} cannot reach the node.
   ====
   --
   
  
positive.code: ====
  
  [id="nodes-edge-remote-workers-strategies-statefulset_{context}"]
  https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/[stateful sets] do not get restarted when there is an outage. The pods remain in the `terminating` state until the control plane can acknowledge that the pods are terminated. 
  
  To avoid scheduling a to a node that does not have access to the same type of persistent storage, {product-title} cannot migrate pods that require persistent volumes to other zones in the case of network separation.
  
  
  
negative.code: 
  [id="nodes-edge-remote-workers-strategies-tolerations_{context}"]
  Tolerations::
  You can use pod tolerations to mitigate the effects if the on-premise node controller adds a `node.kubernetes.io/unreachable` taint with a `NoExecute` effect to a node it cannot reach.
  
  A taint with the `NoExecute` effect affects pods that are running on the node in the following ways:
  
  