<p>I see in the <a href="https://github.com/GoogleCloudPlatform/kubernetes/blob/v0.21.3/docs/volumes.md">docs</a> how do do this for pods, but I want to use a replication controller to manage my pods, ensuring that there is always one up at all times.</p>

<ol>
<li><p>How can I define a replication controller where the pod being run has a persistent volume?</p></li>
<li><p>How is this related to Kubernetes persistentVolumes and persistentVolumeClaims?</p></li>
</ol>

<p>Using a persistent volume in a Replication Controller works great for shared storage.  You include a persistentVolumeClaim in the RC's pod template.  Each pod will use the same claim, which means it's shared storage.  This also works for read-only access in gcloud if your Replica count > 1.</p>

<p>If you wanted distinct volumes per pod, you currently have to create many RCs with Replicas=1 and with distinct persistentVolumeClaims.</p>

<p>We're working out a design for scaling storage through an RC where each pod gets its own volume instead of sharing the same claim.</p>
