Skip to content

Update VPA defaults to 1.5.1 in the vpa-release-1.5 branch#8592

Merged
k8s-ci-robot merged 1 commit into
kubernetes:vpa-release-1.5from
adrianmoisey:bump-to-1.5.1
Oct 2, 2025
Merged

Update VPA defaults to 1.5.1 in the vpa-release-1.5 branch#8592
k8s-ci-robot merged 1 commit into
kubernetes:vpa-release-1.5from
adrianmoisey:bump-to-1.5.1

Conversation

@adrianmoisey
Copy link
Copy Markdown
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

VPA 1.5.1 release, see #8468.

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-area Indicates that a PR should not merge because it lacks an area label. approved Indicates a PR has been approved by an approver from all required OWNERS files. area/vertical-pod-autoscaler Issues or PRs related to the Vertical Pod Autoscaler component labels Sep 30, 2025
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed do-not-merge/needs-area Indicates that a PR should not merge because it lacks an area label. labels Sep 30, 2025
@adrianmoisey
Copy link
Copy Markdown
Member Author

/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Sep 30, 2025
Copy link
Copy Markdown
Member

@omerap12 omerap12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold
/approve

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 30, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrianmoisey, omerap12

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

The pull request process is described here

Details 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

@adrianmoisey
Copy link
Copy Markdown
Member Author

/unhold

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 30, 2025
@adrianmoisey
Copy link
Copy Markdown
Member Author

/test pull-kubernetes-e2e-autoscaling-vpa-full

@adrianmoisey
Copy link
Copy Markdown
Member Author

/lgtm

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

@adrianmoisey: you cannot LGTM your own PR.

Details

In response to this:

/lgtm

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.

@adrianmoisey
Copy link
Copy Markdown
Member Author

@ialidzhikov could you /lgtm ?

containers:
- name: admission-controller
image: registry.k8s.io/autoscaling/vpa-admission-controller:1.5.0
image: registry.k8s.io/autoscaling/vpa-admission-controller:1.5.1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Adrian,

I was wondering if bumping the images in the chart should be before we cut the release. When I checked the release-1.4 branch, I saw that we first bumped the version in vertical-pod-autoscaler/common/version.go. Then , I assume after cutting the release, we bumped the image tag in the manifests.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, that's a great point! Thanks for pointing that out. Let me fix it.

@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 2, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

@adrianmoisey: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubernetes-e2e-autoscaling-vpa-full 5fa2370 link false /test pull-kubernetes-e2e-autoscaling-vpa-full

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.

Copy link
Copy Markdown
Contributor

@ialidzhikov ialidzhikov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 2, 2025
@adrianmoisey
Copy link
Copy Markdown
Member Author

/test pull-kubernetes-e2e-autoscaling-vpa-full

@k8s-ci-robot k8s-ci-robot merged commit 76cdef4 into kubernetes:vpa-release-1.5 Oct 2, 2025
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/vertical-pod-autoscaler Issues or PRs related to the Vertical Pod Autoscaler component cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants