mongodb / helm-charts

Apache License 2.0
99 stars 92 forks source link

statefulset - storageclass values set on values.yaml not considered #300

Closed ajay15283 closed 6 months ago

ajay15283 commented 10 months ago

Hello Team,

I am trying to add statefulset related values specifically to add custom storage class name on the values.yaml but it seems to be pick the default values and failing to create pvc which makes pods to pending

Please find the attached values.yaml

# Deploys MongoDB with `resource` attributes.
createResource: true
resource:
  name: mongodb-replica-set
  version: 4.4.0
  members: 3
  tls:
    enabled: false

    # Installs Cert-Manager in this cluster.
    useX509: false
    sampleX509User: false
    useCertManager: true
    certificateKeySecretRef: tls-certificate
    caCertificateSecretRef: tls-ca-key-pair
    certManager:
      certDuration: 8760h   # 365 days
      renewCertBefore: 720h   # 30 days

  users: []
  # if using the MongoDBCommunity Resource, list any users to be added to the resource
  # users:
  # - name: my-user
  #   db: admin
  #   passwordSecretRef: # a reference to the secret that will be used to generate the user's password
  #     name: <secretName>
  #   roles:
  #     - name: clusterAdmin
  #       db: admin
  #     - name: userAdminAnyDatabase
  #       db: admin
  #     - name: readWriteAnyDatabase
  #       db: admin
  #     - name: dbAdminAnyDatabase
  #       db: admin
  #   scramCredentialsSecretName: my-scram
  statefulSet:
    spec:
      volumeClaimTemplates:
        - metadata:
            name: data-volume
          spec:
            storageClassName: nfs-csi
        - metadata:
            name: logs-volume
          spec:
            storageClassName: nfs-csi
github-actions[bot] commented 7 months ago

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

github-actions[bot] commented 6 months ago

This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.