<p>I configured in the <code>hazelcast.xml</code> file of my microservice a list like following</p>
<pre class="lang-xml prettyprint-override"><code>&lt;list name=&quot;listA&quot;&gt;
    &lt;statistics-enabled&gt;false&lt;/statistics-enabled&gt;
    &lt;backup-copy&gt;1&lt;/backup-copy&gt;
&lt;list&gt;
</code></pre>
<p>When I deployed the microservice on k8s cluster with replicas=2, I was expecting that the values of <code>listA</code> are shared to both pods, meaning that when <code>pod-0</code> add an entry to <code>listA</code> that entry will be visible for <code>pod-1</code>. But I found that each pod has its own separate instance and I am not sure why, any help/suggestion is appreciated.</p>
<p>Or should I use Hazelcast's <code>IMap</code> instead?</p>

MedMahmoud
<p>Have your pods formed a cluster ?</p>
<p>Do you get a message in the logs such as:</p>
<pre><code>Members {size:2, ver:2} [
    Member [12.34.56.001]:5701 - 7ee6659e-620c-4db6-b348-8769000c2b0a
    Member [12.34.56.002]:5701 - 41238cc4-ef9a-4d50-94a7-a8fab67f43de this
]
</code></pre>
<p>If you see <code>size:2</code> it's a cluster of two pods. If it's a cluster of two pods, your <code>listA</code> should be accessible from both.</p>
<p>If you have <code>replicas==2</code> then you'll get two pods, but if they can't find each other they'll form two clusters of one pod rather than one cluster of two pods.</p>
<p>You need to check the discovery section for Kubernetes. See <a href="https://docs.hazelcast.com/hazelcast/5.1/deploy/configuring-kubernetes" rel="nofollow noreferrer">here</a>.
The easiest way is to turn off multicast, turn on Kubernetes, use the default namespace and a service name. Once you have that running you can expand to
different namespaces, roles, operators, helm charts, etc.</p>
<p><a href="https://guides.hazelcast.org/kubernetes/" rel="nofollow noreferrer">This guide</a> might help also.</p>
