This repository has been archived by the owner on May 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Metricbeat] DNS lookup failure for node host #394
Labels
Comments
Hi there, I was wondering if anyone knew of a manual fix for this (while the bug is being tackled). |
Hi there, any news here? |
For me the workaround/fix was to add the following options to the daemonset template: spec:
template:
spec:
hostNetwork: true
dnsPolicy: ClusterFirstWithHostNet
containers: |
4 tasks
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@FedeBev That didn't help for me. My spec for the agents is this one:
kube-state-metrics was installed |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Chart version: 7.4.1
Kubernetes version: 1.14.2
Kubernetes provider: Digital Ocean
Helm Version: 2.13
helm get release
outputDescribe the bug:
Metricbeat with default chart values fails to resolve node hosts.
Steps to reproduce:
Expected behavior:
I expected to see actual metrics of the listed pods.
metricbeat logs:
Any additional context:
The text was updated successfully, but these errors were encountered: