GKE部署Elasticsearch StatefulSet时PVC绑定失败问题求助

我在Google Kubernetes Engine（GKE）部署2副本的Elasticsearch StatefulSet，已准备好部署文件、PV和Service清单。第一个Pod运行正常，但第二个Pod始终处于Pending状态。查看Pod描述提示：

0/2 nodes are available: pod has unbound immediate PersistentVolumeClaims

检查PVC时发现错误：

Reason FailedBinding:Messagevolume "elasticsearch-pv" already bound to a different claim.

我的疑问：明明StatefulSet里用volumeClaimTemplates只请求PV中10Gi容量的3Gi，为什么会出现这个问题？该怎么解决？

我的PersistentVolume YAML文件 #

apiVersion: v1
kind: PersistentVolume
metadata:
 name: elasticsearch-pv
 namespace: elk
spec:
 capacity:
   storage: 10Gi
 accessModes:
 - ReadWriteOnce
 nfs:
   path: /filestore_vol1/elastic-gke/
   server: 10.x.x.122

我的StatefulSet YAML文件 #

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: elasticsearch-cluster
  namespace: elk
spec:
  serviceName: elasticsearch
  replicas: 2
  selector:
    matchLabels:
      app: elasticsearch
  template:
    metadata:
      labels:
        app: elasticsearch
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: app-elk
                operator: In
                values:
                - "elastic-tomcat"
      containers:
      - name: elasticsearch
        image: elasticsearch:7.17.5
        imagePullPolicy: Always
        resources:
            limits:
              cpu: 1000m
            requests:
              cpu: 200m
        ports:
        - containerPort: 9200
          name: rest
          protocol: TCP
        - containerPort: 9300
          name: inter-node
          protocol: TCP
        volumeMounts:
        - name: data
          mountPath: /usr/share/elasticsearch/data
        env:
          - name: cluster.name
            value: elasticsearch-cluster
          - name: node.name
            valueFrom:
              fieldRef:
                fieldPath: metadata.name
          - name: discovery.seed_hosts
            value: "elasticsearch-cluster-0.elasticsearch,elasticsearch-cluster-1.elasticsearch"
          - name: cluster.initial_master_nodes
            value: "elasticsearch-cluster-0"
          - name: ES_JAVA_OPTS
            value: "-Xms512m -Xmx512m"
          - name: network.host
            value: "0.0.0.0"
      initContainers:
      - name: fix-permissions
        image: busybox
        command: ["sh", "-c", "chown -R 1000:1000 /usr/share/elasticsearch/data"]
        securityContext:
          privileged: true
        volumeMounts:
        - name: data
          mountPath: /usr/share/elasticsearch/data
      - name: increase-vm-max-map
        image: busybox
        command: ["sysctl", "-w", "vm.max_map_count=262144"]
        securityContext:
          privileged: true
      - name: increase-fd-ulimit
        image: busybox
        command: ["sh", "-c", "ulimit -n 65536"]
        securityContext:
          privileged: true
  volumeClaimTemplates:
  - metadata:
      name: data
      labels:
        app: elasticsearch
    spec:
      accessModes: [ "ReadWriteOnce" ]
      storageClassName: ""
      volumeName: elasticsearch-pv
      resources:
        requests:
          storage: 3Gi

错误截图 #

• 你在volumeClaimTemplates中硬指定了volumeName: elasticsearch-pv，这会强制所有由该模板生成的PVC都尝试绑定到同一个PV上，但Kubernetes的PV与PVC是一对一绑定关系，一旦第一个Pod的PVC成功绑定该PV，第二个PVC就无法再绑定，直接导致绑定失败。
• 即便PV剩余容量足够，Kubernetes也不允许一个PV被多个PVC共享，这是PV/PVC模型的核心规则，和容量剩余多少无关。

方案1：移除volumeName，让K8s自动绑定（推荐） #

修改StatefulSet的volumeClaimTemplates，删除volumeName: elasticsearch-pv这一行，同时准备两个符合要求的PV（每个容量≥3Gi），或者配置StorageClass实现动态PV创建，这样每个Pod的PVC会自动匹配并绑定到对应的PV上。

修改后的volumeClaimTemplates片段：

volumeClaimTemplates:
- metadata:
    name: data
    labels:
      app: elasticsearch
  spec:
    accessModes: [ "ReadWriteOnce" ]
    storageClassName: ""
    resources:
      requests:
        storage: 3Gi

如果使用动态PV，可部署NFS存储提供者（如nfs-subdir-external-provisioner）并创建对应StorageClass，无需手动创建PV，K8s会自动为每个PVC生成独立PV。

方案2：手动创建两个独立PV #

若坚持用静态PV，需创建两个独立的PV，每个对应Elasticsearch节点的独立存储目录：

第一个PV（对应node-0）：

apiVersion: v1
kind: PersistentVolume
metadata:
 name: elasticsearch-pv-0
 namespace: elk
spec:
 capacity:
   storage: 3Gi
 accessModes:
 - ReadWriteOnce
 nfs:
   path: /filestore_vol1/elastic-gke/node-0/
   server: 10.x.x.122

第二个PV（对应node-1）：

apiVersion: v1
kind: PersistentVolume
metadata:
 name: elasticsearch-pv-1
 namespace: elk
spec:
 capacity:
   storage: 3Gi
 accessModes:
 - ReadWriteOnce
 nfs:
   path: /filestore_vol1/elastic-gke/node-1/
   server: 10.x.x.122

之后移除StatefulSet中的volumeName配置，让PVC自动绑定到这两个PV上。

重要注意事项 #

• Elasticsearch集群的每个节点必须使用独立存储，绝对不能共享PV，否则会引发数据冲突、集群脑裂甚至数据损坏。
• NFS存储需为每个节点创建独立的目录，避免多个Pod读写同一目录。

内容的提问来源于stack exchange，提问作者dante alighieri