Kubernetes：无法将未格式化的卷挂载为只读

Question

我正在尝试将 gcePersistentDisk 用作 ReadOnlyMany，以便我在多个节点上的 pod 可以读取该磁盘上的数据。 按照此处的文档进行相同操作。

要创建并稍后格式化 gce 永久磁盘，我已按照此处文档中的说明进行操作。 在这个文档之后，我进入了其中一个节点并格式化了磁盘。 请参阅下面的完整错误以及其他 yaml 文件。

kubectl describe pods -l podName

Name:               punk-fly-nodejs-deployment-5dbbd7b8b5-5cbfs
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               gke-mycluster-default-pool-b1c1d316-d016/10.160.0.12
Start Time:         Thu, 25 Apr 2019 23:55:38 +0530
Labels:             app.kubernetes.io/instance=punk-fly
                    app.kubernetes.io/name=nodejs
                    pod-template-hash=1866836461
Annotations:        kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for container nodejs
Status:             Pending
IP:
Controlled By:      ReplicaSet/punk-fly-nodejs-deployment-5dbbd7b8b5
Containers:
  nodejs:
    Container ID:
    Image:          rajesh12/smartserver:server
    Image ID:
    Port:           3002/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False

    Restart Count:  0
    Requests:
      cpu:  100m
    Environment:
      MYSQL_HOST:           mysqlservice
      MYSQL_DATABASE:       app
      MYSQL_ROOT_PASSWORD:  password
    Mounts:
      /usr/src/ from helm-vol (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-jpkzg (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  helm-vol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  my-readonly-pvc
    ReadOnly:   true
  default-token-jpkzg:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-jpkzg
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                  Age               From                                               Message
  ----     ------                  ----              ----                                               -------
  Normal   Scheduled               2m                default-scheduler                                  Successfully assigned default/punk-fly-nodejs-deployment-5dbbd7b8b5-5cbfs to gke-mycluster-default-pool-b1c1d316-d016
  Normal   SuccessfulAttachVolume  1m                attachdetach-controller                            AttachVolume.Attach succeeded for volume "pvc-9c796180-677e-11e9-ad35-42010aa0000f"
  Warning  FailedMount             10s (x8 over 1m)  kubelet, gke-mycluster-default-pool-b1c1d316-d016  MountVolume.MountDevice failed for volume "pvc-9c796180-677e-11e9-ad35-42010aa0000f" : failed to mount unformatted volume as read only
  Warning  FailedMount             0s                kubelet, gke-mycluster-default-pool-b1c1d316-d016  Unable to mount volumes for pod "punk-fly-nodejs-deployment-5dbbd7b8b5-5cbfs_default(86293044-6787-11e9-ad35-42010aa0000f)": timeout expired waiting for volumes to attach or mount for pod "default"/"punk-fly-nodejs-deployment-5dbbd7b8b5-5cbfs". list of unmounted volumes=[helm-vol]. list of unattached volumes=[helm-vol default-token-jpkzg]

只读_pv.yaml

apiVersion: v1
kind: PersistentVolume
metadata:
  name: my-readonly-pv
spec:
  storageClassName: ""
  capacity:
    storage: 1G
  accessModes:
    - ReadOnlyMany
  gcePersistentDisk:
    pdName: mydisk0
    fsType: ext4
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-readonly-pvc
spec:
  accessModes:
    - ReadOnlyMany
  resources:
    requests:
      storage: 1G

部署.yaml

  volumes:
    - name: helm-vol
      persistentVolumeClaim:
        claimName: my-readonly-pvc
        readOnly: true
  containers:
    - name: {{ .Values.app.backendName }}
      image: "{{ .Values.image.repository }}:{{ .Values.image.tagServer }}"
      imagePullPolicy: {{ .Values.image.pullPolicy }}
      env:
      - name: MYSQL_HOST
        value: mysqlservice
      - name: MYSQL_DATABASE
        value: app
      - name: MYSQL_ROOT_PASSWORD
        value: password
      ports:
        - name: http-backend
          containerPort: 3002
      volumeMounts:
        - name: helm-vol
          mountPath: /usr/src/

Answer 1

听起来您的PVC正在动态配置未使用默认 StorageClass格式化的新卷

可能是您的 Pod 是在与您配置PV的位置不同的可用性中创建的。 gce 卷有多个 Pod 读取器的问题是 Pod 必须始终位于同一可用区。

一些选项：

• 只需在您的节点所在的同一可用区上创建和格式化PV 。

• 当你定义你的 PV 时，你可以指定Node Affinity以确保它总是被分配给一个特定的节点。

• 定义一个指定文件系统的StorageClass

   kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: mysc provisioner: kubernetes.io/aws-ebs parameters: type: gp2 fsType: ext4

  然后在你的 PVC 中使用它：

   apiVersion: v1 kind: PersistentVolumeClaim metadata: name: my-pvc spec: accessModes: - ReadOnlyMany resources: requests: storage: 1G storageClassName: mysc

  该卷将自动配置和格式化。

Answer 2

我在尝试使用ReadWriteOnce访问模式配置永久性磁盘时收到了相同的错误消息。 为我解决问题的是从部署规范的volumes声明中删除属性readOnly: true 。 对于您的deployment.yaml文件，这将是这个块：

volumes:
- name: helm-vol
  persistentVolumeClaim:
    claimName: my-readonly-pvc
    readOnly: true

尝试删除该行并查看错误是否消失。

Answer 3

我遇到了同样的错误，并设法使用有关使用预先存在的磁盘的相关文章中的几行来修复它https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/preexisting-pd

您需要将storageClassName和volumeName添加到持久卷声明中：

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pv-claim-demo
spec:
  # It's necessary to specify "" as the storageClassName
  # so that the default storage class won't be used, see
  # https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1
  storageClassName: ""
  volumeName: pv-demo
  accessModes:
    - ReadOnlyMany
  resources:
    requests:
      storage: 500G