Minikube下MongoDB Community K8s Operator绑定自定义PV失败问题

问题原因 #

你当前配置存在3个核心冲突/错误，导致PVC无法匹配预创建的PV：

1. 重复配置持久化规则：同时定义了podSpec.persistence和statefulSet.spec.volumeClaimTemplates，Operator会优先解析内置的podSpec.persistence字段，自定义的卷声明模板会被覆盖不生效
2. PV配置错误：PV是集群级资源，不需要配置namespace字段，且你未配置回收策略，可能出现绑定后自动回收的问题
3. 访问模式不匹配：你创建的PV仅支持ReadWriteOnce，但PVC配置了ReadWriteOnce、ReadWriteMany两种模式，访问模式不一致会导致无法匹配

修复步骤 #

1. 修正PV配置

删除PV的namespace字段，添加回收策略配置，完整配置如下：

apiVersion: v1
kind: PersistentVolume
metadata:
  name: mongodb-pv-00
  labels: 
    type: local
    service: mongo
spec:
  storageClassName: manual
  persistentVolumeReclaimPolicy: Retain
  capacity:
    storage: 5Gi
  accessModes:
  - ReadWriteOnce
  hostPath: 
    path: "/mnt/mongodata/00"
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mongodb-pv-01
  labels: 
    type: local
    service: mongo
spec:
  storageClassName: manual
  persistentVolumeReclaimPolicy: Retain
  capacity:
    storage: 5Gi
  accessModes:
  - ReadWriteOnce
  hostPath: 
    path: "/mnt/mongodata/01"
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mongodb-pv-02
  labels: 
    type: local
    service: mongo
spec:
  storageClassName: manual
  persistentVolumeReclaimPolicy: Retain
  capacity:
    storage: 5Gi
  accessModes:
  - ReadWriteOnce
  hostPath: 
    path: "/mnt/mongodata/02"

执行kubectl apply -f pv.yaml完成PV更新。

2. 修正MongoDB副本集CR配置

删除重复的podSpec.persistence字段，调整PVC访问模式和PV对齐，完整配置如下：

apiVersion: mongodbcommunity.mongodb.com/v1
kind: MongoDBCommunity
metadata:
  name: mongo-rs
  namespace: $NAMESPACE
spec:
  members: 3
  type: ReplicaSet
  version: "4.4.0"
  persistent: true
  statefulSet:
    spec:
      volumeClaimTemplates:
        - metadata:
            name: data-volume
          spec:
            accessModes: [ "ReadWriteOnce" ]
            resources:
              requests:
                storage: 5Gi
            selector:
              matchLabels:
                type: local
                service: mongo
            storageClassName: manual
  security:
    authentication:
      modes: ["SCRAM"]
  users:
    - ... # 保持你原有的用户配置不变
  additionalMongodConfig:
    storage.wiredTiger.engineConfig.journalCompressor: zlib

3. 前置环境检查&重新部署

• 先在Minikube节点创建对应的存储目录并授权，避免权限报错：
  minikube ssh "sudo mkdir -p /mnt/mongodata/{00,01,02} && sudo chmod 777 /mnt/mongodata/*"
• 删除之前部署失败产生的未绑定PVC：
  kubectl delete pvc -l app=mongodb-svc -n $NAMESPACE
• 重新apply MongoDB CR配置即可。

内容的提问来源于stack exchange，提问作者Federico Barusco