-
Notifications
You must be signed in to change notification settings - Fork 449
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
Can not deploy MinIO Operator and Tenant version 5.0.2 together in one chart due to CRD #1553
Comments
I'm also experiencing this issue when trying to bootstrap a cluster. Do we have a workaround in the meantime? I've tried to copy the CRDs to the |
@AlexGodbehere I did not copy CRD in my deployment chart but I took official chart and moved the crd from templates to crds only for testing purpose, to verify the assumption. |
Any update on this? |
Gentle Reminder!!! |
Please refer to the Helm article about CRD handling, read it. https://github.com/helm/community/blob/f9e06c16d89ccea1bea77c01a6a96ae3b309f823/architecture/crds.md Basically it states "it's not that simple", CRD management comes with a series of problems mentioned in the document. We moved the CRD's from the
Take the risk of provoke this scenario for the purpose of have a umbrella chart is probably not worth. Possible solutionProbably create a third helm repo containing only the CRD's and make it a dependency of the For now, move the CRD's to the |
Please re-open if the problem is persisting |
CRD install issues are still being reported, see #1915, I am reopening this issue |
Maybe we can use our code to update the CRD. If someone have a old one. @pjuarezd |
I am working on MinIO Operator and Tenant Chart version 5.0.2 to deploy on Kubernetes.
When I am deploying Operator first and then Tenant as a separate deployment everything works as expected with no issue.
But I want to create a single chart which has dependency on both Operator and Tenant chart and can be deployed together.
This creates problem as while installing because CRD is missing (not yet created).
To confirm this, I moved the CRD in operator chart from templates to crds folder and it worked as expected even when both charts deployed together.
Note that reason for deploying them together is because MinIO along with few other charts are parts of the infra and deploying everything individually is not very user friendly so I created an umbrella chart that can deploy everything.
Expected Behavior
We should be able to deploy both charts together in single deployment without failure.
Current Behavior
Helm Installation fails with following error when both Operator and Tenant are deployed in single release.
Error from Helm Installation:
Possible Solution
Earlier Charts from MinIO had CRDs located under crds folder so helm was installing them first, now that it is under templates helm is not installing them before other resources.
Steps to Reproduce (for bugs)
Context
MinIO along with few other charts are parts of the infra and deploying everything individually is not very user friendly so I created an umbrella chart that can deploy everything.
Regression
Not sure from which version this was changed but I remember earlier version had CRDs in the crds folder and not in templates.
Your Environment
MinIO Operator and Tenant Chart Version : 5.0.2
Helm Version: v3.10.2
Kubernetes Version: 1.26.0
Operating System in Kubernetes Node: Ubuntu 2204
As Both charts are working individually I do not have any specific changes in deployment values. The problems is only when they are deployed together.
The text was updated successfully, but these errors were encountered: