title: Kubernetes message consumer scalability
body: <p>How To deploy in kubernetes a message consumer for kafka, amqp or any other message broker which scales up and down ? My hypothesis is that the consumer runs a loop which pulls messages.</p>
  
  <p>I d like kubernetes To create more pods when many messages arrive in the broker queue and remove some pods when too few messages arrive in the queue.</p>
  
  <p>Which component has the initiative of the ending of the pods? The pod itself because it can't fetch a message from the queue? Or kubernetes because the pod doesnt consume cpu?</p>
  
  <p>If any pod ends when the queue is empty, i m afraid that pods Will keep born and die as long as the queue is empty.</p>