Google Cloud 上的持久卷 Kubernetes答案

【问题标题】：Persistent volume Kubernetes on Google CloudGoogle Cloud 上的持久卷 Kubernetes
【发布时间】：2026-01-06 15:20:07
【问题描述】：

我在 Google Cloud 上的 Kubernetes 集群上有一个 Redis pod。我已经建立了 PV 和声明。


   
kind: PersistentVolume
apiVersion: v1
metadata:
 name: redis-pv
 labels:
   type: local
spec:
 storageClassName: manual
 capacity:
   storage: my-size 
 accessModes:
   - ReadWriteOnce
 hostPath:
   path: "/data"
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
 labels:
   app: postgres
 name: redis-pv-claim
spec:
 storageClassName: manual
 accessModes:
 - ReadWriteOnce
 resources:
   requests:
     storage: my size 
I also mounted it in my deployment.yaml

volumeMounts:
     - mountPath: /data
       name: redis-pv-claim
   volumes:
   - name: redis-pv-claim
     persistentVolumeClaim:
       claimName: redis-pv-claim

运行describe pod时看不到任何错误



Volumes:
 redis-pv-claim:
   Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
   ClaimName:  redis-pv-claim
   ReadOnly:   false

但它无法保存任何密钥。每次部署后，“/data”文件夹都是空的。

我的 NFS 现在处于活动状态，但我仍然无法保留数据。

描述PVC


Namespace:     my namespace 
StorageClass:  nfs-client
Status:        Bound
Volume:        pvc-5d278b27-a51e-4262-8c1b-68b290b21fc3
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
              pv.kubernetes.io/bound-by-controller: yes
              volume.beta.kubernetes.io/storage-class: nfs-client
              volume.beta.kubernetes.io/storage-provisioner: cluster.local/ext1-nfs-client-provisioner
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      1Gi
Access Modes:  RWX
VolumeMode:    Filesystem
Mounted By:    my grafana pod
Events:        <none>

Describe pod 给了我一个错误。


Warning  FailedMount  18m   kubelet, gke-devcluster-pool-1-36e6a393-rg7d  MountVolume.SetUp failed for volume "pvc-5d278b27-a51e-4262-8c1b-68b290b21fc3" : mount failed: exit status 1
Mounting command: systemd-run
Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/8f7b6630-ed9b-427a-9ada-b75e1805ed60/volumes/kubernetes.io~nfs/pvc-5d278b27-a51e-4262-8c1b-68b290b21fc3 --scope -- /
home/kubernetes/containerized_mounter/mounter mount -t nfs 192.168.1.21:/mnt/nfs/development-test-claim-pvc-5d278b27-a51e-4262-8c1b-68b290b21fc3 /var/lib/kubelet/pods/8f7b6630-ed9b-427a-9ada-b75e1805ed60
/volumes/kubernetes.io~nfs/pvc-5d278b27-a51e-4262-8c1b-68b290b21fc3
Output: Running scope as unit: run-ra5925a8488ef436897bd44d526c57841.scope
Mount failed: mount failed: exit status 32
Mounting command: chroot

【问题讨论】：

通过查看第一个 YAML ，您使用的主机路径卷仅在每次部署后位于同一节点上时才会保留。您没有在 redis 部署中使用 NFS，因此这两个问题似乎无关。另外，您描述了哪个 pod 并且您的标签显示 postgres ，请尝试重新描述您的问题以更有意义。
请检查this docs 并按照@tarun khosla 的建议澄清您的问题。

标签： kubernetes google-compute-engine google-kubernetes-engine

【解决方案1】：

在 GKE 上使用 PV 和 PVC 使用 redis

apiVersion: v1
kind: Service
metadata:
  name: redis
spec:
  type: LoadBalancer
  ports:
  - port: 6379
    name: redis
  selector:
    app: redis
---
apiVersion: apps/v1beta2
kind: StatefulSet
metadata:
  name: redis
spec:
  selector:
    matchLabels:
      app: redis  
  serviceName: redis
  replicas: 1
  template:
    metadata:
      labels:
        app: redis 
    spec:
      containers:
        - name: redis
          image: redislabs/rejson
          args: ["--requirepass", "password", "--appendonly", "no", "--loadmodule", "/usr/lib/redis/modules/rejson.so"]
          ports:
            - containerPort: 6379
              name: redis
          resources:
            limits:
              cpu: .50
              memory: 1500Mi
            requests:
              cpu: .25
              memory: 1000Mi
          volumeMounts:
            - name: redis-volume
              mountPath: /data
  volumeClaimTemplates:
  - metadata:
      name: redis-volume
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 5Gi

您可以根据需要更新此状态集中的图像。

【讨论】：