Monitor kubernetes ingress resources with heartbeat

Elastic Stack Beats
1

Is there any way to configure heartbeat to automatically detect the ingress resources in a cluster and run a simple health-check against each of them ?

Also, the heartbeat chart deploys a daemonset; is this really needed ? I get a lot of redundant data. And it scales with the cluster. Wouldn't a deployment with 2 replicas be more appropriate ?

2

What do you mean about ingress resources? Do you mean the endpoints heartbeat checks? I assume you've read our autodiscover docs already?

You're 100% right about the daemonset. We are targeting the new scope option for autodiscover in 7.6 (see the docs here), which let you look at the whole k8s cluster instead of just a single pod.

Also, which chart are you using? Is it https://github.com/helm/charts/tree/master/stable/heartbeat or https://helm.elastic.co

3

What do you mean about ingress resources? Do you mean the endpoints heartbeat checks? I assume you've read our autodiscover docs already?

I mean k8s resources of ingress type, as per Ingress | Kubernetes
I checked the autodiscoder docs, I hope I did not miss anything. And then I checked the codebase and my understanding is it's only watching pods, services and nodes https://github.com/elastic/beats/blob/master/libbeat/autodiscover/providers/kubernetes/kubernetes.go#L104

Also, which chart are you using? Is it https://github.com/helm/charts/tree/master/stable/heartbeat or https://helm.elastic.co

This one. https://github.com/helm/charts/tree/master/stable/heartbeat But I ended up doing my own manifests in order to move from DaemonSet to Deployment.

4

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