<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>Addressing your question about memory of the second pod, the second <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod/" rel="nofollow noreferrer">pod</a> will be assigned a new memory.</p>

<p>Addressing your question about the replicated memory content of the new pod, all the new pod will be replicated depending on the container spec. </p>

<p>Addressing your question about shared memory between pods, no the memory is not shared between the pods.If you want to share elements between pods, you need to make sure it is in container spec, such as <a href="https://kubernetes.io/docs/concepts/storage/volumes/" rel="nofollow noreferrer">volume</a> or <a href="https://kubernetes.io/docs/tasks/inject-data-application/define-environment-variable-container/" rel="nofollow noreferrer">environment variables</a>.</p>

<p>Addressing your question about key values, if you are looking for storage solutions, you could consider volumes <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod/" rel="nofollow noreferrer">1</a>, <a href="https://kubernetes.io/docs/concepts/storage/volumes/" rel="nofollow noreferrer">2</a>. If you are just looking to pass some key-values to pods, you might consider using <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/" rel="nofollow noreferrer">configmaps</a>.</p>

<p><a href="https://kubernetes.io/docs/concepts/workloads/pods/pod/" rel="nofollow noreferrer">1</a> <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/storage/persistent-volumes/</a></p>

<p><a href="https://kubernetes.io/docs/concepts/storage/volumes/" rel="nofollow noreferrer">2</a> <a href="https://kubernetes.io/docs/concepts/storage/" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/storage/</a></p>
