title: Allow only one pod of a type on a node in Kubernetes
body: <p>How to allow only one pod of a type on a node in Kubernetes. Daemon-sets doesn't fit into this use-case.</p>
  
  <p>For e.g. - Restricting scheduling of only one Elasticsearch pod on a node, to prevent data loss in case the node goes down.</p>
  
  <p>It can be achieved by carefully planning CPU/memory resource of pod and machine type of cluster.</p>
  
  <p>Is there any other way to do so?</p>