<p>On my Kubernetes cluster on GKE, I have the following persistent volume claims (PVCs):</p>

<pre><code>kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: registry
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 100Gi
</code></pre>

<p>and:</p>

<pre><code>kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: postgresql-blobs
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 100Gi
</code></pre>

<p>Amongst others, I have the following persistent volume defined:</p>

<pre><code>kind: PersistentVolume
apiVersion: v1
metadata:
  name: pv0003
spec:
  capacity:
    storage: 100Gi
  accessModes:
    - ReadWriteOnce
    - ReadOnlyMany
  gcePersistentDisk:
    pdName: registry
    fsType: ext4
</code></pre>

<p>Now, both claims claimed the same volume:</p>

<pre><code>bronger:~$ kubectl describe pvc postgresql-blobs registry
Name:           postgresql-blobs
Namespace:      default
Status:         Bound
Volume:         pv0003
Labels:         &lt;none&gt;
Capacity:       100Gi
Access Modes:   RWO,ROX


Name:           registry
Namespace:      default
Status:         Bound
Volume:         pv0003
Labels:         &lt;none&gt;
Capacity:       100Gi
Access Modes:   RWO,ROX
</code></pre>

<p>Funny enough, the PV knows only about one of the claims:</p>

<pre><code>bronger:~$ kubectl describe pv pv0003
Name:           pv0003
Labels:         &lt;none&gt;
Status:         Bound
Claim:          default/postgresql-blobs
Reclaim Policy: Retain
Access Modes:   RWO,ROX
Capacity:       100Gi
Message:
Source:
    Type:       GCEPersistentDisk (a Persistent Disk resource in Google Compute Engine)
    PDName:     registry
    FSType:     ext4
    Partition:  0
    ReadOnly:   false
</code></pre>

<p>How can I prevent this from happening?</p>

<p>This is a bug and is fixed by <a href="https://github.com/kubernetes/kubernetes/pull/16432" rel="nofollow">https://github.com/kubernetes/kubernetes/pull/16432</a></p>
