-
Notifications
You must be signed in to change notification settings - Fork 64
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
Error creating CRD when reusing helm install on different namespaces #452
Comments
ok i got it, i have to set serviceAccount: but now i get an error with the annotation MutatingWebhookConfiguration helm.release which is not matching the new namespace |
You only need to install Operator once and it can manage emqx in different namespaces |
thanks for the reply. I will take note of it. I am not fully aware of which version i am using, but i know i am using the chart v2.0.1 from https://repos.emqx.io/charts and to setup the cluster i am using the EMQX CRD, not EMQBroker, so i guess i am using v5 - 2lapha1 , am i correct? basically my second question on how to create users via the operator boils down to the more generic question: what can we do with the operator at all? "just" controlling the cluster nodes or also ACL, topics, configs, etc? i have to say, i am still new to EMQX and i am evaluating its usage for cloud based application. |
This depends on the version of EMQX you are deploying, in |
In addition to this, EMQX Operator also offers a number of operational and maintenance features. For example, when you update the EMQX listener using the EMQX 5 Dashboard, the EMQX Operator will automatically update the K8S service |
so you mean that creating ACL and topics is possible via defining the right CRD? is there any documentation for that ? |
Maybe you can check EMQX Documentation: https://www.emqx.io/docs/en/v5.0/admin/cfg.html |
i think this issue can be closed and our discussion moved to: #451 (comment) |
OK, let me close this issue |
The first time i run helm install everything goes smoothly, i.e. the CRD are installed and all the rest deployed.
when i run helm install on a different namespace, setting the value skipCRDs to true, i get an error of ownership in the cluster role ... how to fix?
The text was updated successfully, but these errors were encountered: