anchor.diff:  
   [NOTE]
   ====
  -Static pods cannot use secrets and config maps. 
  +Static pods cannot use secrets and config maps.
   ====
   
   [id="nodes-edge-remote-workers-strategies-zones_{context}"]
  
positive.code: - key: "node.kubernetes.io/unreachable"
    operator: "Exists"
    effect: "NoExecute" <1>
    tolerationSeconds: 0
  - key: "node.kubernetes.io/not-ready"
    operator: "Exists"
    effect: "NoExecute" <2>
    tolerationSeconds: 0
  ...
  ----
  <1> The `NoExecute` effect with `tolerationSeconds`: 0 allows pods to remain if the control plane cannot reach the node.
  <2> The `NoExecute` effect with `tolerationSeconds`: 0 allows pods to remain if the control plane marks the node as `Unhealthy`.
  
  {product-title} uses the `tolerationSeconds` value after the `pod-eviction-timeout` value elapses.  
  
  Other types of {product-title} objects::
  You can use replica sets, deployments, and replication controllers. The scheduler can reschedule these pods onto other nodes after the node is disconnected for five minutes. Rescheduling onto other nodes can be beneficial for some workloads, such as REST APIs, where an administrator can guarantee a specific number of pods are running and accessible.
  
negative.code:       effect: NoSchedule
  ----
  
  * 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.
  
  [NOTE]
  ====
  Daemon sets do not schedule pods after a reboot of the node if {product-title} cannot reach the node.
  ====
  --
  
  