Configure metric discovery to use same defaults that are in official kubernetes integration config about prometheus-adapter HOT 3 CLOSED

We don't necessarily want to autoinject the pod name at that label, because you might have metrics coming from one pod which describe another (e.g. coming from an ingress controller, describing ingress objects), and you don't want those metrics being associated in the API with the original pod, or overwriting the listed pod with the pod the metrics came from.

from prometheus-adapter.

@DirectXMan12 Cool. I knew there was a reason, just wanted to understand what it was.

from prometheus-adapter.

@DirectXMan12 @itskingori I encountered same issue that message "metric xxx not registered" from function QueryForMetric, which caused metric discovery functionality doesn't work by using default prometheus-kubernetes.yml, then I try add --label-prefix=kubernetes_, it still did not work, only patch prometheus-kubernetes.yml diff provide by @itskingori can workaround.

I think the root cause is that you can't use --label-prefix=kubernetes_ to map kubernetes_ namespaces and kubernetes_pod_name` in the same time. (take job_name: 'kubernetes-pods' as an example)

from prometheus-adapter.