<p>I am a Kubernetes noobie so my apologies if this is a basic question - I am trying to get a good understanding of this amazing technology.</p>

<p>Let's say I have some processing on a pod and I have some variables and arrays. Now I will have a heavy load, and a new pod will be dispensed/replicated - now I have 2 pods rather than 1 to handle my load. What will happen to the memory of the second pod? Is pod 2 replicated with the same memory contents? will memory be shared? If there is some communication across my microservices which requires memory to be consistent, in other words there is some variables dependency, then replicating a pod with fresh memory is catastrophic. For clarifcation, let us say there is a key, value map on one pod. A pod is replicated, then we have two key,value map (one on pod1 and another on pod2). But we want a key,value map containing all the data that is common between these two pods - a shared key,value map across replicated pods - NOT two isolated key,value maps.</p>

<p>Sure, I suppose one solution would be to have a shared, central, database for reference. But this is a massive overhead for situations where we just want to share an array of a few hundred elements! What is the Kubernetes approach to this issue?</p>

<p>@Zeruno maybe i am thinking out loud here but what if you used the existing <code>etcd</code> cluster as a key-value store for your application </p>

<ol>
<li><p>No overhead of maintaining it since its already there and manged by K8s itself 
that too in a distributed cluster mode. </p></li>
<li><p>This might act as a single point of storage that will be accessible by all the pods in that cluster.</p></li>
</ol>
