[bot] [main] Automated version update

[prom-op-bot]

Description

This is an automated version and jsonnet dependencies update performed from CI.

Please review the following changelogs to make sure that we don't miss any important
changes before merging this PR.

https://github.com/grafana/grafana/releases/tag/v10.4.2 https://github.com/prometheus/node_exporter/releases/tag/v1.8.0 https://github.com/prometheus/prometheus/releases/tag/v2.52.0 https://github.com/prometheus-operator/prometheus-operator/releases/tag/v0.73.2 https://github.com/brancz/kube-rbac-proxy/releases/tag/v0.17.1

Configuration of the workflow is located in .github/workflows/versions.yaml.

Type of change

• NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry

[kakkoyun]

@metalmatze I think something has changed in node-mixin, and e2e tests are failing, no?

[rgarcia89]

@kakkoyun I don't see any other tests failing besides the security run. However, these tests have been failing for quite some time now. So, in general, they shouldn't be related to this PR

[philipgough]

hey sorry for the lag on this. yeah I think this is fine. merging

[philipgough]

lgtm

[kakkoyun]

Something must have changed. Thanks to whoever fixed it 🎉

[rgarcia89]

Careful with the update to prometheus v2.52.0. I am seeing the following since the update in the logs which is triggering the PrometheusDuplicateTimestamps rule.

ts=2024-05-13T09:06:22.827Z caller=scrape.go:1738 level=warn component="scrape manager" scrape_pool=serviceMonitor/monitoring/kube-state-metrics/0 target=https://10.244.1.208:8443/metrics msg="Error on ingesting samples with different value but same timestamp" num_dropped=1
ts=2024-05-13T09:06:52.930Z caller=scrape.go:1738 level=warn component="scrape manager" scrape_pool=serviceMonitor/monitoring/kube-state-metrics/0 target=https://10.244.1.208:8443/metrics msg="Error on ingesting samples with different value but same timestamp" num_dropped=1

Downgrading to prometheus v2.51.2 fixed it for now.

[TeslaHan]

Careful with the update to prometheus v2.52.0. I am seeing the following since the update in the logs which is triggering the PrometheusDuplicateTimestamps rule.

ts=2024-05-13T09:06:22.827Z caller=scrape.go:1738 level=warn component="scrape manager" scrape_pool=serviceMonitor/monitoring/kube-state-metrics/0 target=https://10.244.1.208:8443/metrics msg="Error on ingesting samples with different value but same timestamp" num_dropped=1
ts=2024-05-13T09:06:52.930Z caller=scrape.go:1738 level=warn component="scrape manager" scrape_pool=serviceMonitor/monitoring/kube-state-metrics/0 target=https://10.244.1.208:8443/metrics msg="Error on ingesting samples with different value but same timestamp" num_dropped=1

Downgrading to prometheus v2.51.2 fixed it for now.

Hello! I am currently using Prometheus version 2.54.1 and I am still experiencing the error message "Error on ingesting samples with different value but same timestamp" with a num_dropped value of 5. How can I resolve this issue?

[rgarcia89]

See here kubernetes/kube-state-metrics#2390

[TeslaHan]

请参阅此处kub​​ernetes/kube-state-metrics#2390

I'm sorry, but I still don't understand the link and haven't solved my problem yet. I have created an issue, and I would appreciate your guidance. Thank you!
Error on ingesting samples with different value but same timestamp #2577