Having troubles installing Heartbeat on AKS

I've been trying pretty hard to install heartbeat but so far aint working.

All our Elasticsearch stack is being installed through helm charts successfully. Apparently heartbeat doesn't have an official helm chart yet (am I wrong?).

I did find a heartbeat helm chart which seems not to belong to elasticsearch team https://github.com/helm/charts/tree/master/stable/heartbeat but as much as I try to install it it just doesn't work as expected. It seems that the installation happens but the configurations I added into my heartbeat.values.yml aren't taken into consideration (index names, hosts to be monitored...).

Whenever I connect in the underlying AKS layer into the container with kubectl exec and I check the heartbeat.yml file it seems standard without the configurations I have provided so I am here wondering:

Which one is the right way to install heartbeat into my AKS?

We don't have anything official ATM, but we are working on adding a manifest. You can track progress here: https://github.com/elastic/beats/issues/17752

Hello @Andrew_Cholakian1,
Thank you for replying.
Is there any forecast (Q3, Q4) of when this will be done?

I'm not sure, but I believe @exekias would know

Thank you @Andrew_Cholakian1
@exekias - do you have a timeline?

We now have a pull request up here: https://github.com/elastic/beats/pull/17928 , so it hopefully won't be too much longer.

Will follow up. Hopefully the helm package won’t take too long to be released as well.

Heartbeat chart isn't on our roadmap currently, but there is https://github.com/elastic/helm-charts/issues/317 to track this request.

Don't hesitate to add a :+1: to the issue.

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.