Replies: 4 comments 6 replies
-
Hi @erezblm The limitation on the number of Core nodes is only for high availability. If you do want to have only one Core node, a hack method is to directly modify the CRD file of EMQX to meet your requirements. However, I believe that in most cases, two Core nodes will not consume too many resources.
No, you should just check "Ready", if didn't changing into Ready, maybe EMQX Operator have some bug. If you set volumeClaimTemplates in EMQX customer resource, then it's a know issue, I'm fixed it in 2.2.1-rc.1, if not, please open Operator's debug log and share it with me, you can append |
Beta Was this translation helpful? Give feedback.
-
oh yes, i have used volumeClaimTemplates. Regarding the minimum 2 replicas, sure i've set it to 2 for now (even though they'll be running on the same node). |
Beta Was this translation helpful? Give feedback.
-
thanks you! |
Beta Was this translation helpful? Give feedback.
-
Hi @erezblm the EMQX Operator 2.2.1 is released, in 2.2.1, EMQX Operator will no longer check the number of core nodes, and fixed #897 (comment), could you please try it :) |
Beta Was this translation helpful? Give feedback.
-
Hey, I'm deploying the EMQX with the new operator 2.2.0 with the new apiversion "apps.emqx.io/v2beta1"
and when deploying just a single core replicate i received the following error:
admission webhook "validator.apps.emqx.io" denied the request: the number of EMQX core nodes must be greater than 1
I understand the need from more than 1 replicas for production, but for the dev environment it helps us to save resources.
Is there any particular reason for the new restriction?
And another question, have you changed the infla ready state into "CoreNodesReady" instead of "Ready"? For some reason It's not changing into Ready, so my deployment is waiting for that although everything looks just fine (BTW i'm deploying 0 replicas for my development environment so it might be related.).
Thanks, Erez.
Beta Was this translation helpful? Give feedback.
All reactions