Kubernetes k8s无法在GCP上调度本地ssd卷

我正在尝试将Google云中的本地SSD指定为

PersistedVolume

。我按照设置，运行

kubectl get pv

返回一个有效卷：

NAME                CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM     STORAGECLASS   REASON    AGE
local-pv-9721c951   368Gi      RWO            Delete           Available             local-scsi               1h

问题是我无法让我的吊舱绑定到它。kubectl get pvc的

NAME      STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS   AGE
mapdata   Pending                                       local-scsi     7m

而
kubectl get events
为我提供了以下信息：

LAST SEEN   FIRST SEEN   COUNT     NAME                                                KIND                    SUBOBJECT   TYPE      REASON                 SOURCE                        MESSAGE
7m          7m           1         v3tiles.1551c0bbcb23d983                            Service                             Normal    EnsuredLoadBalancer    service-controller            Ensured load balancer
2m          8m           24        maptilesbackend-8645566545-x44nl.1551c0ae27d06fca   Pod                                 Warning   FailedScheduling       default-scheduler             0/1 nodes are available: 1 node(s) didn't find available persistent volumes to bind.
2m          8m           26        mapdata.1551c0adf908e362                            PersistentVolumeClaim               Normal    WaitForFirstConsumer   persistentvolume-controller   waiting for first consumer to be created before binding

我需要做什么才能将SSD绑定到我的pod？以下是我一直在尝试的代码：

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: maptilesbackend
  namespace: default
spec:
  selector:
    matchLabels:
      app: maptilesbackend
  strategy:
    type: RollingUpdate
  template:
    metadata:
      labels:
        app: maptilesbackend
    spec:
      containers:
      - image: klokantech/openmaptiles-server
        imagePullPolicy: Always
        name: maptilesbackend
        volumeMounts:
          - mountPath: /data
            name: mapdata
            readOnly: true
      volumes:
        - name: mapdata
          persistentVolumeClaim:
            claimName: mapdata
            readOnly: true
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: "local-scsi"
provisioner: "kubernetes.io/no-provisioner"
volumeBindingMode: "WaitForFirstConsumer"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mapdata
spec:
  storageClassName: local-scsi
  accessModes:
    - ReadOnlyMany
  resources:
    requests:
      storage: 300Gi

事实证明，
accessMode:ReadOnlyMany
在这种情况下不起作用。不知道如何让它工作。。。如果我找到更多信息，我将发布。
ReadOnlyMany
对本地SSD没有意义

根据文件：

ReadOnlyMany–卷可以由多个节点以只读方式装入

您不能在多个节点上安装本地SSD，因为它仅在一个节点上安装。
根据以下GCE，可以通过单个节点以ReadWriteOnce或多个节点以ReadOnlyMany的形式安装磁盘。因此，对于单个节点，ReadOnlyMany并不合适。