kubernetes - 部署和PVC

Question

我有以下 PersistentVolumeClaim :

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: nginx-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 256Mi
  storageClassName: fask

和部署:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  replicas: 2
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.7.9
        ports:
        - containerPort: 80
        volumeMounts:
        - name: data
          mountPath: "/var/www/html"
      volumes:
      - name: data
        persistentVolumeClaim:
          claimName: nginx-pvc

如果我使用单个副本运行Deployment，我的PV将由vsphere StorageClass 动态创建

但是，如果我有两个以上的副本，它将无法创建第二个PV:

AttachVolume.Attach failed for volume "pvc-8facf319-6b1a-11e8-935b-00505680b1b8" : Failed to add disk 'scsi0:1'.
Unable to mount volumes for pod "nginx-deployment-7886f48dcd-lzms8_default(b0e38764-6b1a-11e8-935b-00505680b1b8)": timeout expired waiting for volumes to attach or mount for pod "default"/"nginx-deployment-7886f48dcd-lzms8". list of unmounted volumes=[data]. list of unattached volumes=[data default-token-5q7kr]

Answer 1

However, if I have more than 2 replicas it will fail to create the second PV

然后，您可能应该在其中使用StatefulSet和volumeClaimTemplates而不是Deployment和PersistentVolumeClaim。

在您的情况下，每个部署都具有相同的PersistentVolumeClaim(即ReadWriteOnly，并且无法在第二个请求上挂载)，而使用volumeClaimTemplates时，每个副本提供了一个不同的资源。