-
I'll write how I wen't about it : I was looking for a way to deploy EMQX 5 to Azure Kubernetes service and found EMXQ Operator, great. Went on to read 'Getting Started', deployed with the example stated here, great. It deploys and it seems that it works. Then, searching for something else, found this ; 'Deployment on Public Cloud - Azure AKS'. Here it says to first create a storageClass 'azurefile-csi-nfs'. Also, the example is with emqx-ee and with an older version of the operator (apiversion of v1beta3) and an older version of emqx (4.4.8). So, what am I missing here :
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi, @KlemenDanfoss thanks for your feedback, we will update documents soon.
Yes, just use
StorageClass holds EMQX runtime data, such as configuration changes made via the EMQX Dashboard, etc. If storageClass is not enabled, then when the EMQX CR is removed and redeployed, you will get a completely new cluster.
Please check https://github.com/emqx/emqx-operator/blob/main/config/samples/emqx/v2alpha1/emqx-full.yaml, and change the |
Beta Was this translation helpful? Give feedback.
Hi, @KlemenDanfoss thanks for your feedback, we will update documents soon.
Let's back to your concerns:
Yes, just use
kind: EmqxBroker
replace ofkind: EmqxEnterprise
, and it will workStorageClass holds EMQX runtime data, such as configuration changes made via the EMQX Dashboard, etc. If storageClass is not enabled, then when the EMQX CR is removed and redeployed, you will get a completely new cluster.
More info, please check https://docs.emqx.com/en/emqx-operator/latest/tasks/configure-emqx-…