chore(deps): update helm release kube-prometheus-stack to v60.0.2

[renovate]

This PR contains the following updates:

Package	Update	Change
kube-prometheus-stack (source)	patch	60.0.0 -> 60.0.2

---

Release Notes

prometheus-community/helm-charts (kube-prometheus-stack)

v60.0.2

Compare Source

v60.0.1

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

• [kube-prometheus-stack] bump thanos to 0.35.1 by @​DrFaust92 in https://github.com/prometheus-community/helm-charts/pull/4596

Full Changelog: prometheus-community/helm-charts@kube-state-metrics-5.20.0...kube-prometheus-stack-60.0.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	1, because the PR involves a simple version bump in a Helm chart configuration file, which is straightforward to verify and does not involve complex code changes.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

Code feedback:

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Pin the Helm chart version to a specific range to allow automatic patch updates Consider pinning the Helm chart version to a more specific version range instead of a single version to allow for automatic patch updates without breaking changes. This can help in maintaining the stability of the deployment while still receiving important updates. observability/base/kube-prometheus-stack/helmrelease.yaml [14] -version: "60.0.1" +version: "~60.0" Suggestion importance[1-10]: 8 Why: Pinning the Helm chart version to a specific range can help maintain the stability of the deployment while still allowing for important updates. This is a best practice that can prevent breaking changes while ensuring the system remains up-to-date.	8