Skip to content

Conversation

@SuperQ
Copy link

@SuperQ SuperQ commented Aug 27, 2025

What problem does this PR solve?

Monitoring component versions are years out of date.

What is changed and how does it work?

Update several monitoring component versions to current releases.

  • Prometheus v2.27.1 -> v3.5.0
  • Thanos v0.17.2 -> v0.39.2
  • Prometheus Config Reloader v0.49.0 -> v0.85.0

This imports countless bug fixes and feature improvements. For example, Prometheus is over 2x as memory efficient as the previous versions, has support for native histograms, and full container memory/cpu limit awareness.

Code changes

  • Has Go code change
  • Has CI related scripts change

Tests

  • Unit test
  • E2E test
  • Manual test
  • No code

Side effects

  • Breaking backward compatibility
  • Other side effects:

Related changes

  • Need to cherry-pick to the release branch
  • Need to update the documentation

Release Notes

Please refer to Release Notes Language Style Guide before writing the release note.


Update several monitoring component versions to current releases.
* Prometheus v2.27.1 -> v3.5.0
* Thanos v0.17.2 -> v0.39.2
* Prometheus Config Reloader v0.49.0 -> v0.85.0

This imports countless bug fixes and feature improvements. For example,
Prometheus is over 2x as memory efficient as the previous versions, has
support for native histograms, and full container memory/cpu limit
awareness.

Signed-off-by: SuperQ <[email protected]>
@ti-chi-bot ti-chi-bot bot requested a review from shonge August 27, 2025 13:01
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Aug 27, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tennix for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Aug 27, 2025

Hi @SuperQ. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Aug 27, 2025

Welcome @SuperQ! It looks like this is your first PR to pingcap/tidb-operator 🎉

@pingcap-cla-assistant
Copy link

pingcap-cla-assistant bot commented Aug 27, 2025

CLA assistant check
All committers have signed the CLA.

@ti-chi-bot ti-chi-bot bot added the size/L label Aug 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant