K8s autodiscovery for filebeat?

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Does anyone please have the remotest clue how to find out what this means when trying to use K8s autodiscovery for filebeat?

Exiting: error in autodiscover provider settings: 
error setting up kubernetes autodiscover provider: 
unable to build kube config due to error: 
invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable
2

Is there any extra information in the events? It sounds like your node doesn't have a need environmental variable for autodiscover.

3

What "events"?

I've got Prometheus doing K8s autodiscover perfectly happily on the same cluster BTW.

4

It turned out that adding automountServiceAccountToken: true made a difference.

That wasn't a very helpful error message, was it?

5

Looks like you found a solution, in the future, if you get a less-than-helpful k8s CRD deployment, you might find extra information in kubectl get events Application Introspection and Debugging | Kubernetes In my experience of debugging random ECK CRDs that's been pretty helpful.

6

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