1
我有以下pvc
(永久卷索赔):如果持久性卷被删除并重新创建,Kubernetes持久性卷声明会再次绑定吗?
piVersion: v1
kind: PersistentVolumeClaim
metadata:
name: test-claim-web
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
和谷歌云支持pv
(持久卷):
apiVersion: v1
kind: PersistentVolume
metadata:
name: test-pv-1
spec:
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
gcePersistentDisk:
pdName: test-1
fsType: ext4
和存在的磁盘在谷歌的云。
如果我首先创建pv
和pvc
后,kubectl get pvc,pv
将显示:
NAME STATUS VOLUME CAPACITY ACCESSMODES AGE
test-claim-web Bound test-pv-1 10Gi RWO 15s
NAME CAPACITY ACCESSMODES STATUS CLAIM REASON AGE
test-pv-1 10Gi RWO Bound default/test-claim-web 25s
但是,如果我删除并重新创建pv
,kubectl get pvc,pv
将显示:
NAME STATUS VOLUME CAPACITY ACCESSMODES AGE
test-claim-web Bound test-pv-1 10Gi RWO 3m
NAME CAPACITY ACCESSMODES STATUS CLAIM REASON AGE
test-pv-1 10Gi RWO Available 18s
- 为什么
pvc
仍然Bound
? - 不是
pvc
(重新)自动绑定? (我还观察到,pvc
后创建pv
使得pvc
与Pending
状态永远等待。)
我用下面的Kubernetes版本:
Client Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.4", GitCommit:"3eed1e3be6848b877ff80a93da3785d9034d0a4f", GitTreeState:"clean"}
Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.4", GitCommit:"3eed1e3be6848b877ff80a93da3785d9034d0a4f", GitTreeState:"clean"}