Update module k8s.io/autoscaler/vertical-pod-autoscaler to v1.7.0 - #51852
Update module k8s.io/autoscaler/vertical-pod-autoscaler to v1.7.0#51852renovate[bot] wants to merge 1 commit into
Conversation
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
PRApprover will approve and merge this PR, FAQ, #dx-source-code-management 🛠️ PRApproval Status
➡️ Current phase: CI tests failed. Please fix the failing tests to continue. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7bde5851c9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| k8s.io/apimachinery v0.35.5 | ||
| k8s.io/autoscaler/vertical-pod-autoscaler v1.6.0 | ||
| k8s.io/apimachinery v0.36.1 | ||
| k8s.io/autoscaler/vertical-pod-autoscaler v1.7.0 |
There was a problem hiding this comment.
Include InPlace in VPA update-mode metrics
With this dependency bump, VPA v1.7.0 adds the UpdateModeInPlace value, but the kube-state-metrics custom VPA collector still hard-codes only the previous modes in pkg/collector/corechecks/cluster/ksm/customresources/vpa.go:119-125. On clusters using spec.updatePolicy.updateMode: InPlace, kube_verticalpodautoscaler_spec_updatepolicy_updatemode will emit 0 for every update_mode label instead of exposing the configured mode, so dashboards/monitors cannot distinguish this supported v1.7 setting. Please extend the mode list and tests alongside the module bump.
Useful? React with 👍 / 👎.
This comment has been minimized.
This comment has been minimized.
b01a8fa to
755058d
Compare
393785a to
4d3afb3
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
devflow unqueued this merge request: It did not become mergeable within the expected time |
48d7fcf to
d967920
Compare
new commit added, dismiss all previous approvals
d94af2b to
69a717c
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
devflow unqueued this merge request: It did not become mergeable within the expected time |
69a717c to
9feee6d
Compare
new commit added, dismiss all previous approvals
9feee6d to
726827d
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
PR already in the queue with status waiting |
726827d to
bd9af2c
Compare
new commit added, dismiss all previous approvals
8445e89 to
c1f42ca
Compare
|
This pull request has been automatically marked as stale because it has not had activity in the past 15 days. It will be closed in 30 days if no further activity occurs. If this pull request is still relevant, adding a comment or pushing new commits will keep it open. Also, you can always reopen the pull request if you missed the window. Thank you for your contributions! |
This PR contains the following updates:
v1.6.0→v1.7.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Configuration
📅 Schedule: (in timezone Europe/Paris)
* 0-4,22-23 * * 1-5)* * * * 0,6)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.