如何在K8S的Elasticsearch集群中为不同Pod配置不同存储挂载？

• AWS EBS卷默认仅支持ReadWriteOnce（RWO）访问模式，同一时间只允许挂载到单个EC2节点，哪怕是同节点的多个Pod共用同块EBS存储不同路径，也会导致ES节点数据冲突，完全不符合ES集群的高可用部署要求。
• 你当前的StatefulSet配置全局绑定了固定PVCebs-claim，所有3个副本Pod都会尝试挂载同一个PVC对应的EBS卷，必然触发Multi-Attach错误。

删除StatefulSet里硬编码的全局volumes下的persistent-storage配置，替换为volumeClaimTemplates字段，让K8s自动为每个es-0、es-1、es-2副本创建独立的PVC，每个PVC绑定单独的EBS卷，这是StatefulSet部署有状态集群的标准方案。

修正后的完整配置 #

apiVersion: v1
kind: ConfigMap
metadata:
  name: es-config
data:
  elasticsearch.yml: |
    cluster.name: elk-cluster
    network.host: "0.0.0.0"
    bootstrap.memory_lock: false
    node.max_local_storage_nodes: 9
    discovery.seed_hosts:
      - es-0.es-entrypoint.default.svc.cluster.local
      - es-1.es-entrypoint.default.svc.cluster.local
      - es-2.es-entrypoint.default.svc.cluster.local
  # 建议Xms和Xmx设为相同值，避免内存波动影响性能，按你的资源配置调整为8G
  ES_JAVA_OPTS: -Xms8g -Xmx8g
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: es
  namespace: default
spec:
  serviceName: es-entrypoint
  replicas: 3
  selector:
    matchLabels:
      name: es
  template:
    metadata:
      labels:
        name: es
    spec:
      volumes:
        - name: es-config
          configMap:
            name: es-config
            items:
              - key: elasticsearch.yml
                path: elasticsearch.yml
      initContainers:
        - name: permissions-fix
          image: busybox
          volumeMounts:
            - name: persistent-storage
              mountPath: /usr/share/elasticsearch/data
          command: [ 'chown' ]
          args: [ '1000:1000', '/usr/share/elasticsearch/data' ]
      containers:
        - name: es
          image: elasticsearch:7.10.1
          resources:
            requests:
              cpu: 2
              memory: 8Gi
          ports:
            - name: http
              containerPort: 9200
            - containerPort: 9300
              name: inter-node
          volumeMounts:
            - name: es-config
              mountPath: /usr/share/elasticsearch/config/elasticsearch.yml
              subPath: elasticsearch.yml
            - name: persistent-storage
              mountPath: /usr/share/elasticsearch/data
  # 新增动态PVC模板，自动为每个副本创建独立EBS卷
  volumeClaimTemplates:
  - metadata:
      name: persistent-storage
    spec:
      accessModes: [ "ReadWriteOnce" ]
      # 替换为你EKS集群可用的EBS存储类，默认一般为gp2或gp3
      storageClassName: "gp3"
      resources:
        requests:
          storage: 100Gi # 按需调整存储容量
---
apiVersion: v1
kind: Service
metadata:
  name: es-entrypoint
spec:
  selector:
    name: es
  ports:
    - port: 9200
      targetPort: 9200
      protocol: TCP
  clusterIP: None

部署注意事项 #

• 先删除之前创建的ebs-claimPVC和已运行的异常ES Pod，再重新应用修正后的配置
• 生产环境不要尝试将多个ES节点挂载到同一块EBS，单EC2节点故障会导致整个集群不可用，且数据混乱无法恢复。

内容的提问来源于stack exchange，提问作者Joey Yi Zhao