<p>How does pods that are controlled by a replication controller and "hidden" behind a service in Kubernetes write/read data? If I have an application that recieves images from the user that needs to be persisted, where do I store that? Because of the service in front I have no control over which node it is stored at if I use volumes. </p>

<p>I think the "simple" answer to your question is that you will need shared storage under you Kubernetes cluster, so that every pods access the same data. Then it wouldn't matter where the pods are running and which pod is actually executing the service.</p>

<p>May be another solution would be <a href="https://github.com/clusterhq/flocker" rel="nofollow noreferrer">Flocker</a>, they describe themself in short: </p>

<blockquote>
  <p>Flocker is a data volume manager and multi-host Docker cluster management tool. With it you can control your data using the same tools you use for your stateless applications by harnessing the power of ZFS on Linux.</p>
</blockquote>

<p>Anyway I think the storage question on Kubernetes or any other dockerized infrastructure is very interesting. </p>

<p>It looks like the google-app-engine doesn't support sharing data store between their apps by default like they pointed out in this <a href="https://stackoverflow.com/questions/8956230/can-i-access-datastore-entities-of-my-other-google-app-engine-applications">SO Question</a></p>
