kubernetes持久卷读写(RWO)不适用于nfs
那里, 根据该文件:kubernetes持久卷读写(RWO)不适用于nfs,kubernetes,persistent-volumes,persistent-volume-claims,Kubernetes,Persistent Volumes,Persistent Volume Claims,那里, 根据该文件: ReadWriteOnce–卷可以通过单个节点以读写方式装入 我创建了一个基于nfs的PV: apiVersion: v1 kind: PersistentVolume metadata: name: tspv01 spec: capacity: storage: 15Gi accessModes: - ReadWriteOnce persistentVolumeReclaimPolicy: Recycle nfs: path:
ReadWriteOnce–卷可以通过单个节点以读写方式装入
我创建了一个基于nfs的PV:
apiVersion: v1
kind: PersistentVolume
metadata:
name: tspv01
spec:
capacity:
storage: 15Gi
accessModes:
- ReadWriteOnce
persistentVolumeReclaimPolicy: Recycle
nfs:
path: /gpfs/fs01/shared/prod/democluster01/dashdb/gamestop/spv01
server: 169.55.11.79
本PV的PVC:
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: sclaim
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 15Gi
创建PVC绑定到PV后:
root@hydra-cdsdev-dal09-0001:~/testscript# kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESSMODES AGE
sclaim Bound tspv01 15Gi RWO 4m
然后我用同样的PVC制作了两个豆荚:
POD1:
POD2:
创建两个吊舱后,它们被分配到两个不同的节点。我可以执行到容器中,并且可以在nfs挂载的文件夹中读写
root@hydra-cdsdev-dal09-0001:~/testscript# kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE
mypodshared1 1/1 Running 0 18s 172.17.52.7 169.45.189.108
mypodshared2 1/1 Running 0 36s 172.17.83.9 169.45.189.116
有人知道为什么会发生这种情况吗?访问模式取决于存储提供商。对于NFS,它们实际上没有什么不同,但是HostPath应该正确使用这些模式
有关所有各种选项,请参见下表:kubernetes 1.4.5I版也尝试了
hostPath
,nfs也存在同样的问题。。。
kind: Pod
apiVersion: v1
metadata:
name: mypodshared2
labels:
name: frontendhttp
spec:
containers:
- name: myfrontend
image: nginx
ports:
- containerPort: 80
name: "http-server"
volumeMounts:
- mountPath: "/usr/share/nginx/html"
name: mypd
volumes:
- name: mypd
persistentVolumeClaim:
claimName: sclaim
root@hydra-cdsdev-dal09-0001:~/testscript# kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE
mypodshared1 1/1 Running 0 18s 172.17.52.7 169.45.189.108
mypodshared2 1/1 Running 0 36s 172.17.83.9 169.45.189.116