2015-11-14 14 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 

我怎样才能防止这种情况发生?

回答