Adding compatibility with default scrape_configs

[0xbilko]

Adding compatibility with default scrape_configs:

https://github.com/prometheus-community/helm-charts/blob/main/charts/prometheus/values.yaml#L783
https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-agent/values.yaml#L293

[dotdc]

Hi @beliys,

Do you have kubernetes-apiservers as a value in the job label?
Could you share more information on your setup?

If it's the case, I would rather create a job variable like it was the case before.
Let me know if you need help.

[0xbilko]

Hi @dotdc,
That's right, kubernetes-apiservers is the default value if you don't install it through kube-prometheus-stack or victoria-metrics-k8s-stack. And if you install this chart https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus or this https://github.com/VictoriaMetrics/helm-charts/tree/master/charts/victoria-metrics-agent, then you have job=kubernetes-apiservers. Of course, I can override all the rules in the default scrape_configs, but if this PR is not suitable, then it's easier for me to just fork this dashboard. But if you accept this PR, it will allow to use your dashboard in all standard cases, not just when using kube-prometheus-stack or victoria-metrics-k8s-stack.

[dotdc]

🎉 This PR is included in version 2.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[dotdc]

Sure, will probably create a job variable at some point.
Thank you for your contribution!