Closed ReeceKindon closed 9 months ago
Related forum post: https://forum.camunda.io/t/can-simple-monitor-be-deployed-to-aks/1017
@ReeceKindon is this issue still present, or can we close this issue?
No feedback/response. Closing for now. If still relevant, please feel free to re-open.
Hi,
We have successfully deployed Zeebe Cluster & Simple Monitor into AKS using the zeebe/zeebe-cluster-helm & zeebe-simple-monitor-helm charts, but we are struggling connecting the 2 and getting Simple Monitor to start.
The Broker has an initContainer section in the yaml to download the zeebe-hazelcast-exporter.jar and mount at "/exporters" which we can confirm has succeeded via the logs and exec'ing into the Pod's themselves. On the Broker "stateful set" we have added the below env variables:
When starting up Simple Monitor we are able to connect to the Broker fine, but unable to connect to the Hazelcast Exporter. These are our env variables for Simple Monitor deployment:
This is a dump from the logs in Simple Monitor pod:
We are now stuck at this point and despite various attempts to expose port 5701 on the Broker and Gateway and also different connection strings, we haven't had any luck.
Any ideas on what to try next or where this issue resides? Zeebe Broker, Hazelcast Exporter, Zeebe Gateway or Simple Monitor?
Thanks,
Reece