title: Kubernetes node.kubernetes.io/memory-pressure:NoSchedule
body: <p>Good afternoon</p>
  <p>I have two pods that are not lifting due to the following errors:</p>
  <pre><code>prometheus-k8s-0 0/3 Pending 0 56s
  prometheus-k8s-1 2/3 Running 0 69s
  </code></pre>
  <p><code>Warning FailedScheduling &lt;unknown&gt; default-scheduler 0/4 nodes are available: 1 node (s) had taint {node.kubernetes.io/memory-pressure:}, that the pod didn't tolerate, 3 node (s) had volume node affinity conflict</code>.</p>
  <pre><code>kubectl describe nodes aks-bbagentpool-39730754-vmss000000 | grep -i taint
  Taints: node.kubernetes.io/memory-pressure:NoSchedule
  </code></pre>
  <p>I do not see high consumption in any of the nodes:</p>
  <pre><code>kubectl top nodes
  
  NAME CPU (cores) CPU% MEMORY (bytes) MEMORY%
  
  aks-bbagentpool-39730754-vmss000000 153m 8% 920Mi 17%
  aks-bbagentpool-39730754-vmss000001 1854m 97% 5357Mi 99%
  aks-bbinfra-39730754-vmss000000 211m 5% 2038Mi 16%
  aks-bbinfra-39730754-vmss000001 111m 2% 1706Mi 13%
  </code></pre>
  <p>The prometheus solution is from Coreos and I see that the daemonset is operational</p>
  <pre><code>kubectl get daemonsets.apps -n monitoring
  
  NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
  
  node-exporter 4 4 4 4 4 kubernetes.io/os=linux 3d13h
  </code></pre>
  <p>I want to know the reason for this failure and how I can resolve the status of the nodes.</p>