-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
VerneMQ can't create a cluster automatically on Amazon Elastic Kubernetes Service(EKS) #64
Comments
Hi, what does the vernemq logs themselves contain? |
Something is wrong with the VerneMQ nodename configuration. It should be something like Moreover the config |
Yep, I will recommend not using 0.0.0.0 for the clustering interface. Also, I would comment
Also, on the same service that is exposing epmd you need to expose the cluster interface i think:
|
Plus, you need to define a role that allows the MQTT entrypoint to access the kubes API, like:
and after the
Hope this works 🌮 |
First off, really appreciate all of your responses. Based on your suggestions, I updated the YAML file and here is the updated one. I am still not able to see the cluster info.
Here is the cluster status
Here is the logs for POD vernemq-0 and its almost similar (except for POD names) for vernemq-1 & vernemq-2
Some more additional information
|
Your namespace param is still wrong, it should be as I posted above:
That's why you are getting |
@codeadict - Thanks a ton. That works now. I can connect to both mqtt and mqtts. I would really appreciate if I can get any tips on deploying or using this as a highly available production grade VerneMQ instances for a low latency Device Handshakes and Message Deliveries without failure. I do understand that VerneMQ just does that, but wanted to know if there are any other things that I need to take care for a Real World Scenario. |
PLEASE DO NOT MARK THIS AS DUPLICATE AND CLOSE IT, UNLESS THERE IS A COMPLETE SOLUTION TO THIS PROBLEM
Followed the write up from https://github.com/nmatsui/kubernetes-vernemq and followed the issue resolution from #52. In this case, it's not a SSL issue. Trying to do the exact same thing on Amazon EKS.
Here is the YAML file
Kubectl version
The Pods started & ran successfully.
I could not get any cluster.
The Pod's log say nothing.
>kubectl logs vernemq-0
The text was updated successfully, but these errors were encountered: