<p>There is one Kubernetes property called replica, suppose  we have  <code>3</code> replicas(<code>replica-0</code>, <code>replica-1</code>, <code>replica-2</code>) and we are producing 100 messages in Kafka, Only one replica say (<code>replica-0</code>) is invoked at a time for consuming all the 100 messages, but the expected solution is all the 100 messages should be divided among 3 replicas(<code>replica-0</code>, <code>replica-1</code>, <code>replica-2</code>) instead keeping the load on one replica for consuming the messages</p>

jannath hussain
<p>You should clarify &quot;invoked&quot;. Consumers poll; they are not externally &quot;invoked&quot;/started other than calling <code>poll()</code> method.</p>
<p>Consumers configured with the same <code>group.id</code> cannot subscribe to overlapping partitions. If you sent 100 records to one partition, then only one consumer will read that. If you want all applications to read a subset of the data, then you first will need a Kafka topic with at least 3 partitions (the default auto-created topics only have one), then send data amongst those.</p>
<p>Kubernetes has nothing to do with the Kafka consumer subscription.</p>
