Open l15k4 opened 6 years ago
Did you manage to get around this issue?
@edevil No, I didn't, I use --source
additonally prometheus-to-sd only seems to perform source discovery once on startup and won't recognize pods scheduled on the node after startup. This tool would be more useful it was able to monitor dynamic sources in user namespaces. thanks
Hi, I have this DaemonSet :
To run in
default
namespace and it should resolve pods also indefault
namespace, but I cannot force it and I get :which means it tries to do service discovery in the
kube-system
instead ofdefault
... It is hardcoded here forkube-system
https://github.com/GoogleCloudPlatform/k8s-stackdriver/blob/edcfb0bfdb9b25422ed235615b39a4c024d9de09/prometheus-to-sd/config/dynamic_source.go#L17I mean, I'm running this DaemonSet in
default
namespace and all pods that it should discover lives also indefault
namespace, but it has hardcodedkube-system
namespace. Shouldn't it use the--namespace-id
flag instead of it being a constant?