chore(deps): update prom/prometheus docker tag to v3.1.0 #2893
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
| @@ -9,7 +9,7 @@ services: | |||
| volumes: | |||
| - ./conf:/etc/prometheus/ | |||
| - ./prometheus:/prometheus | |||
| image: prom/prometheus:v3.0.1 | |||
| image: prom/prometheus:v3.1.0 | |||
| command: | |||
| - '--config.file=/etc/prometheus/prometheus.yml' | |||
| - '--storage.tsdb.path=/prometheus' | |||
There was a problem hiding this comment.
-
The version change from
v3.0.1tov3.1.0in the provided changeset does not contain any updates that appear critical or significant (e.g., new features, performance improvements, bug fixes). A typical maintenance release usually includes minor improvements rather than major ones without explicit mentions. -
The configuration file and directory paths remain unchanged (
./conf:/etc/prometheus/,./prometheus:/prometheus). This suggests that no additional data or configurations were added or updated between these versions. -
Overall, it appears to be a standard update to use a newer version of Prometheus with minimal modifications. There aren't any noticeable problems related to the image itself but might warrant checking if any specific security patches or other notable features of
v3.1.0differ significantly from v3.0.1 since they're running together in the same container. -
As an optimization suggestion, one could consider reviewing the current environment settings in which this service is deployed. If resources like memory or disk space are at their limits, upgrading the service's version might impact them adversely depending on how resource-intensive Prometheus activities such as processing metrics may grow over time with new releases.
Without access to more context about the deployment setup (like available resources), I cannot make recommendations specifically tailored here, but generally speaking, always prioritize stability when deploying upgrades unless you thoroughly understand and test the implications against your specific infrastructure.
This PR contains the following updates:
v3.0.1->v3.1.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
prometheus/prometheus (prom/prometheus)
v3.1.0: 3.1.0 / 2025-01-02Compare Source
What's Changed
l=~".+"matcher. #15474, #15684absent,absent_over_timeandderivfunc with histograms. #15667resetsfunction for histograms. #15527changes()for mix of histograms and floats. #15469round()function did not remove__name__label. #15250count_valuesfor histograms. #15422boolmodifier and native histograms. #15413Configuration
📅 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: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.