Skip to content

vertical-pod-autoscaler: Fix the k8s.io/client-go version#8579

Merged
k8s-ci-robot merged 2 commits intokubernetes:masterfrom
ialidzhikov:fix/client-go-version
Sep 29, 2025
Merged

vertical-pod-autoscaler: Fix the k8s.io/client-go version#8579
k8s-ci-robot merged 2 commits intokubernetes:masterfrom
ialidzhikov:fix/client-go-version

Conversation

@ialidzhikov
Copy link
Copy Markdown
Contributor

What type of PR is this?

/kind regression

What this PR does / why we need it:

The same as the issues with the VPA 1.4.0 release - see #8165 and #8172.

Which issue(s) this PR fixes:

N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

vertical-pod-autoscaler: Fix the version of the `k8s.io/client-go` module.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/regression Categorizes issue or PR as related to a regression from a prior release. 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. area/vertical-pod-autoscaler Issues or PRs related to the Vertical Pod Autoscaler component and removed do-not-merge/needs-area Indicates that a PR should not merge because it lacks an area label. labels Sep 29, 2025
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 29, 2025
@adrianmoisey
Copy link
Copy Markdown
Member

Thanks! Sorry, that was my bad (again)
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 29, 2025
@ialidzhikov
Copy link
Copy Markdown
Contributor Author

/cherry-pick vpa-release-1.5

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@ialidzhikov: once the present PR merges, I will cherry-pick it on top of vpa-release-1.5 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick vpa-release-1.5

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.

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ialidzhikov, 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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 29, 2025
@k8s-ci-robot k8s-ci-robot merged commit 0db699a into kubernetes:master Sep 29, 2025
7 checks passed
@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

@ialidzhikov: new pull request created: #8581

Details

In response to this:

/cherry-pick vpa-release-1.5

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.

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/regression Categorizes issue or PR as related to a regression from a prior release. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants