vernemqube's Introduction

VerneMQube

VerneMQ on Kubernetes - Auto Discovery Cluster

Prerquisties

First you need a Kubernetes Cluster
Then you need to run Kubernetes Pod IP finder for nodes discovery

NOTE: I didn't managed to make the node discovery work with services because of Erlang Port Mapper daemon logic and Service ClusterIP limitation. If you make it work let me know what did you do.

How to Use

Launch Service
- kubectl create -f vernemq-service.yaml
Launch Deployment
- kubectl create -f vernemq-deployment.yaml

Checking cluster status

kubectl get pods

vernemq-3099899313-7gkrr          2/2       Running   0          17s
vernemq-3099899313-qbi91          2/2       Running   0          17s
vernemq-3099899313-u5rrq          2/2       Running   0          17s
kubernetes-pod-ip-finder-6le9j   1/1       Running   0          4h

kubectl exec vernemq-3099899313-7gkrr vmq-admin cluster status

+------------------+-------+
|       Node       |Running|
+------------------+-------+
|[email protected]| true  |
|[email protected]| true  |
|[email protected]| true  |
+------------------+-------+

vernemqube's People

Stargazers

Watchers

vernemqube's Issues

Finding node using service

Is it possible node discovery by using service IPAddress? If yes, can you please provide some information about that. How we can able to solve this problem. Even I am try it in same way but due to cluster Ip limitation I am unable to even ping from the any of the pod.