Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/minio] Added MINIO_DATA_DIR envVar to standalone and distributed charts that… #23388

Merged
merged 1 commit into from
Feb 15, 2024

Conversation

Mo0rBy
Copy link
Contributor

@Mo0rBy Mo0rBy commented Feb 10, 2024

… uses the value of persistence.mountPath

Description of the change

The changes in this PR make the persistence.mountPath value get passed into the MinIO container environment variable MINIO_DATA_DIR such that data stored within MinIO is stored within the mounted PV and it is persisted correctly.

The relevant PR for the MinIO image that allows the MINIO_DATA_DIR envVar to be configured can be seen here.

Benefits

This change make it easier to configure persistence for the MinIO deployment. It makes sense that the persistence.mountPath directory should be used for the persistence of data and making this change means that the MINIO_DATA_DIR envVar is not required within the extraEnvVars section to achieve proper persistence.

Possible drawbacks

N/A

Applicable issues

Addresses #21757

Additional information

I now that this will definitely work for a Standalone deployment, but I'm not so sure about my changes to the Distributed deployment. I would be happy to revert those changes within the distributed/statefulset.yaml file, but I know the standalone/deployment.yaml changes work.

Here is some evidence of the helm template command with this value set to show the resulting deployment template:
image

No extra values have been added, but I have updated the relevant README section a little bit.

Checklist

  • Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
  • Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
  • Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
  • All commits signed off and in agreement of Developer Certificate of Origin (DCO)

… use the value of persistence.mountPath

Signed-off-by: Will Moorby <will.moorby2@gmail.com>
@carrodher carrodher added verify Execute verification workflow for these changes in-progress labels Feb 11, 2024
@github-actions github-actions bot removed the triage Triage is needed label Feb 11, 2024
@github-actions github-actions bot removed the request for review from carrodher February 11, 2024 09:26
Copy link
Contributor

@FraPazGal FraPazGal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Mo0rBy, I've also checked the statefulset changes and they work as expected so no issues from my side. Thanks again for working on this!

@FraPazGal FraPazGal merged commit 08ae391 into bitnami:main Feb 15, 2024
24 checks passed
joancafom pushed a commit to dalbani/charts that referenced this pull request Feb 22, 2024
… use the value of persistence.mountPath (bitnami#23388)

Signed-off-by: Will Moorby <will.moorby2@gmail.com>
Signed-off-by: Jose Antonio Carmona <jcarmona@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minio solved verify Execute verification workflow for these changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants