2015-11-14 17 views
2

論GKE我Kubernetes集羣,我有以下的持續量的權利要求(室性早搏):如何防止兩卷聲稱在Kubernetes上聲明相同的音量?

kind: PersistentVolumeClaim 
apiVersion: v1 
metadata: 
    name: registry 
spec: 
    accessModes: 
    - ReadWriteOnce 
    resources: 
    requests: 
     storage: 100Gi 

和:

kind: PersistentVolumeClaim 
apiVersion: v1 
metadata: 
    name: postgresql-blobs 
spec: 
    accessModes: 
    - ReadWriteOnce 
    resources: 
    requests: 
     storage: 100Gi 

除其他,我有以下的持續量定義:

現在
kind: PersistentVolume 
apiVersion: v1 
metadata: 
    name: pv0003 
spec: 
    capacity: 
    storage: 100Gi 
    accessModes: 
    - ReadWriteOnce 
    - ReadOnlyMany 
    gcePersistentDisk: 
    pdName: registry 
    fsType: ext4 

,無論權利要求中要求保護的相同的體積:

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


Name:   registry 
Namespace:  default 
Status:   Bound 
Volume:   pv0003 
Labels:   <none> 
Capacity:  100Gi 
Access Modes: RWO,ROX 

夠搞怪,光伏只知道有關要求之一:

bronger:~$ kubectl describe pv pv0003 
Name:   pv0003 
Labels:   <none> 
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 

我怎樣才能防止這種情況發生?

回答