-
Notifications
You must be signed in to change notification settings - Fork 70
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
CRD arangomember is deployed by both charts: kube-arangodb and kube-arangodb-crd #740
Comments
Hello! We want to include CRD creation into It was first step for migration, we will move other charts under kube-arangodb. If order of installation is like described in docs - first Best Regards, |
In my opinion it would be better to separate K8S Cluster admin task and K8S namespace admin tasks as they are different concerns:
Otherwise only a K8S Cluster admin can use the chart |
Hello! We can achieve isolation with this approach - CRD from helm are installed as optional. Currently, it is split like this:
Best Regards, |
Thoughts on adding a helm values to wrap the CRD that can be disabled from the |
Hello! CRD chart is not required anymore. Best, |
The CRD
arangomember
is deployed by both charts: kube-arangodb and kube-arangodb-crd=> the last chart wins
I would suggest that only the chart
kube-arangodb-crd
create CRDs.The text was updated successfully, but these errors were encountered: