EFS持久卷索赔失败

Question

我正在尝试部署nginx应用程序，在EFS文件系统中安装卷。在部署了清单yaml文件之后，我的pod挂起状态，同时我验证了pv/pc，它已经在这里限制了日志。

这里是yam文件pvc和部署yaml文件。

apiVersion: apps/v1
kind: Deployment
metadata: 
  name: nginx
spec: 
  replicas: 1
  selector: 
    matchLabels: 
      app: nginx
  template: 
    metadata: 
      labels: 
        app: nginx
    spec:
      containers: 
        - image: "nginx:latest"
          name: nginx
          ports: 
            - containerPort: 80
              name: nginx
         
          volumeMounts: 
            - mountPath: "/etc/localtime -> /usr/share/zoneinfo/Etc/UTC"
              name: nginx-localtime
            - mountPath: "/var/log/nginx/"
              name: nginx-log
            - mountPath: "/var/log/cache/"
              name: nginx-cache
         
      volumes: 
        - name: nginx-localtime
          persistentVolumeClaim: 
            claimName: nginx-localtime
        - name: nginx-log
          persistentVolumeClaim: 
            claimName: nginx-log
        - name: nginx-cache
          persistentVolumeClaim: 
            claimName: nginx-cache

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: nginx-localtime
spec:
  storageClassName: efs
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Mi
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: nginx-log
spec:
  storageClassName: efs
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Mi
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: nginx-cache
spec:
  storageClassName: efs
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Mi

[root@ip-10-1-2-3 nginx]# kubectl get pvc
NAME              STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
nginx-cache       Bound    pvc-d35df958-1288-4028-bf38-d880ec09824f   10Mi       RWX            efs            49s
nginx-localtime   Bound    pvc-ec5b15c0-a9d1-468a-989c-48a18332bbbb   10Mi       RWX            efs            49s
nginx-log         Bound    pvc-c84f1a46-ceba-4180-a2ce-95e19d3d9614   10Mi       RWX            efs            49s

[root@ip-10-1-2-3 nginx]# kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                     STORAGECLASS   REASON   AGE
pvc-c84f1a46-ceba-4180-a2ce-95e19d3d9614   10Mi       RWX            Delete           Bound    default/nginx-log         efs                     54s
pvc-d35df958-1288-4028-bf38-d880ec09824f   10Mi       RWX            Delete           Bound    default/nginx-cache       efs                     53s
pvc-ec5b15c0-a9d1-468a-989c-48a18332bbbb   10Mi       RWX            Delete           Bound    default/nginx-localtime   efs                     54s

Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  36s (x2 over 36s)  default-scheduler  0/2 nodes are available: 2 persistentvolumeclaim "nginx-localtime" not found.
  Normal   Scheduled         34s                default-scheduler  Successfully assigned default/nginx-5c9777db9b-mjc75 to ip-10-1-2-3.eu-central-1.compute.internal
  Normal   Pulled            31s                kubelet            Successfully pulled image "nginx:latest" in 1.726030163s
  Normal   Pulled            29s                kubelet            Successfully pulled image "nginx:latest" in 1.898012878s
  Normal   Pulling           15s (x3 over 33s)  kubelet            Pulling image "nginx:latest"
  Normal   Created           13s (x3 over 31s)  kubelet            Created container nginx
  Normal   Started           13s (x3 over 31s)  kubelet            Started container nginx
  Normal   Pulled            13s                kubelet            Successfully pulled image "nginx:latest" in 1.580634471s
  Warning  BackOff           12s (x3 over 27s)  kubelet            Back-off restarting failed container

我无法理解后，包皮聚氯乙烯，但我的恩吉克斯吊舱不上来，你能不能请一些人帮助我这一点。

Answer 1

PV和PVC有一对一的映射。也就是说，只有一个PVC可以与一个PV结合。首先，检查您是否有3 PV为3 PV，您正试图绑定。

kubectl get pv

还请注意，一旦您删除了一个PVC，它相应的PV是不可用的边界，正如人们可能预期的。根据我的经验，您必须创建一个新的PV和PVC。此外，您也可以在您的PVC yaml中提到PV的名称，如下所示。

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: <your-pvc-name>
spec:
  volumeName: <your-pv-name>
  accessModes:
    - ReadWriteMany
  storageClassName: efs-sc
  resources:
    requests:
      storage: 10Gi