The sentence you cite describes push-model metrics (such as Telegraf writing to InfluxDB). For Prometheus, which uses the pull model, yes – a service is the recommended way to go. Alternatively you can also use the pod discovery in Prometheus to select pods based on their labels, but it just moves the complexity into the Prometheus configuration.
/MR On Wed, Sep 27, 2017 at 8:56 AM Viral Kamdar <viral.kam...@gmail.com> wrote: > The documentation for DaemonSets say that *Pods in the DaemonSet are > configured to send updates to another service, such as a stats database. *Can > someone guide me on how to achieve this? > I have a telegraf container inside my daemonset. I want to use telegraf > metrics in prometheus inside a different pod. Can I do this without > creating a new service for the DS? > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
