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

Document Helm Deploy/Upgrade for MinIO Operator #1021

Closed
5 tasks
ravindk89 opened this issue Oct 4, 2023 · 1 comment · Fixed by #1060
Closed
5 tasks

Document Helm Deploy/Upgrade for MinIO Operator #1021

ravindk89 opened this issue Oct 4, 2023 · 1 comment · Fixed by #1060

Comments

@ravindk89
Copy link
Collaborator

Summary

We have a growing userbase relying on the MinIO Operator Helm Charts for deployment.
As part of supporting that, we need to bring in the Helm-based deploy/upgrade process to the web docs.

A few collected notes:

  • Clusters using helm for tenant management should not use the kubectl minio CLI, as it can result in condition/race issues that conflict with chart-based management tools (ArgoCD)

Goals

List the in-scope goals

  • Add Deploy/Manage/Upgrade/Delete tutorials based on Helm
  • Create a Helm chart reference
  • [ ]

Non-Goals

  • Complete reference of values.yaml
  • A discussion of how Helm charts work
  • A discussion of the community helm chart

List any items that are out of scope

Additional context
Add any other context or screenshots about the feature request here.

@cniackz
Copy link
Contributor

cniackz commented Oct 5, 2023

Adding more information, when using ArgoCD with Helm, you don't have to use minio plugin for k8s because it is a racing condition between ArgoCD and the plugin itself. If for instance you need to upgrade the minio image, all you have to do is change the tenant chart on your Git repository and then Synch via ArgoCD.

ravindk89 added a commit that referenced this issue Nov 16, 2023
Closes #1021 
Closes #1055 
Closes #968 
Closes #943 


---------

Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Pedro Juarez <pjuarezd@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants