You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey Mateo, I've just been following your (excellent) Kubernetes Monitoring with Prometheus tutorial and encountered an issue towards the end, where you deploy the node-exporter DaemonSet:
Here you mention to create a new namespace and pull a DaemonSet from another repo:
Unfortunately the repo is archived and seems to have some issues. In this case, the node-exporter pod created by the DaemonSet is not discoverable by Prometheus because of the seperate monitoring namespace (all previous resources have been launched in default).
For it to work, I had to create a headless Service for the pod:
Hey Mateo, I've just been following your (excellent) Kubernetes Monitoring with Prometheus tutorial and encountered an issue towards the end, where you deploy the node-exporter DaemonSet:
Here you mention to create a new namespace and pull a DaemonSet from another repo:
Unfortunately the repo is archived and seems to have some issues. In this case, the
node-exporter
pod created by the DaemonSet is not discoverable by Prometheus because of the seperatemonitoring
namespace (all previous resources have been launched indefault
).For it to work, I had to create a headless Service for the pod:
which makes it discoverable via DNS in the
prometheus.yml
:You might want to consider including it in the tutorial :)
The text was updated successfully, but these errors were encountered: