Skip to content

[VPA] Enable multiple revive rules - 4#9155

Merged
k8s-ci-robot merged 7 commits intokubernetes:masterfrom
mayuka-c:add-revive-rules-part4
Feb 17, 2026
Merged

[VPA] Enable multiple revive rules - 4#9155
k8s-ci-robot merged 7 commits intokubernetes:masterfrom
mayuka-c:add-revive-rules-part4

Conversation

@mayuka-c
Copy link
Contributor

@mayuka-c mayuka-c commented Feb 1, 2026

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Enables multiple revive rules.
Below are the revive linter rules enabled as part of this PR
- name: redefines-builtin-id
- name: redundant-import-alias

Which issue(s) this PR fixes:

Updates #8986

Special notes for your reviewer:

Continuation from this PR.

image

Does this PR introduce a user-facing change?

NONE

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


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-area area/vertical-pod-autoscaler kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API labels Feb 1, 2026
@k8s-ci-robot
Copy link
Contributor

Hi @mayuka-c. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. and removed do-not-merge/needs-area labels Feb 1, 2026
@k8s-ci-robot k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Feb 1, 2026
@mayuka-c
Copy link
Contributor Author

mayuka-c commented Feb 1, 2026

/cc @adrianmoisey @omerap12

admissionv1 "k8s.io/api/admission/v1"
apiv1 "k8s.io/api/core/v1"
v1 "k8s.io/apimachinery/pkg/apis/meta/v1"
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Based on the comments here, have enabled the "redundant-import-alias" rule

@k8s-triage-robot
Copy link

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Feb 1, 2026
@adrianmoisey
Copy link
Member

Hmmm, I guess the generated files should be excluded from the linting

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 4, 2026
@mayuka-c mayuka-c force-pushed the add-revive-rules-part4 branch from c9230c9 to 18a813a Compare February 4, 2026 14:30
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 4, 2026
@mayuka-c
Copy link
Contributor Author

mayuka-c commented Feb 4, 2026

Hmmm, I guess the generated files should be excluded from the linting

Yes right. Currently I have not changed anything in generated files (Didnt face any lint rule issues) for now. Maybe later we can try excluding linter rules on Generated file?

@mayuka-c
Copy link
Contributor Author

mayuka-c commented Feb 4, 2026

@adrianmoisey @omerap12 Have rebased the PR. PTAL

@adrianmoisey
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 7, 2026
"fmt"

v1 "k8s.io/api/admission/v1"
corev1 "k8s.io/api/core/v1"
Copy link
Member

Choose a reason for hiding this comment

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

I'm taking a look at the kubernetes repo, and it seems that this package is often called corev1, any reason why this changes to apiv1 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

When I looked across the repo, most of the places we have used apiv1, so I have used this to make it consistent.
PLMK if we want to have corev1

Copy link
Member

Choose a reason for hiding this comment

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

corev1 would be great, thanks

Copy link
Contributor Author

Choose a reason for hiding this comment

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

WIll be making the changes, Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done made the updates

"context"

v1 "k8s.io/api/admission/v1"
apiv1 "k8s.io/api/admission/v1"
Copy link
Member

Choose a reason for hiding this comment

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

Should this be admissionv1 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oops my bad, I will update it

@adrianmoisey
Copy link
Member

So this change is huge, but something I really want merged. It's likely that when this PR lands, many other PRs will require a rebase, I chatted a bit to Omer about this, and we decided to only merge this after the CPU boost PR has landed. That PR has been in the works for a while now and is code complete, so it should be merged in the next day or two.

This may cause merge conflicts on your PR (sorry about that!), but we can try get it merged in after that.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 15, 2026
@mayuka-c mayuka-c force-pushed the add-revive-rules-part4 branch from 184ab59 to 9acace5 Compare February 17, 2026 06:29
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Feb 17, 2026
@mayuka-c
Copy link
Contributor Author

Looks like few things got messed up while rebasing, let me try to fix it

@mayuka-c mayuka-c force-pushed the add-revive-rules-part4 branch from 9acace5 to 34c5c9b Compare February 17, 2026 06:35
@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 17, 2026
@mayuka-c mayuka-c force-pushed the add-revive-rules-part4 branch from 34c5c9b to 64db58d Compare February 17, 2026 06:56
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 17, 2026
@mayuka-c
Copy link
Contributor Author

@adrianmoisey PR is ready!
I have rebased with the latest CPU boost commits and fixed the lints with all latest changes.

@adrianmoisey
Copy link
Member

Let's do it!

/lgtm

/cc @omerap12

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 17, 2026
Copy link
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.

/approve

@adrianmoisey
Copy link
Member

/approve

(for hack/OWNERS)

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrianmoisey, mayuka-c, 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 Feb 17, 2026
@k8s-ci-robot k8s-ci-robot merged commit 068565c into kubernetes:master Feb 17, 2026
13 checks passed
@mayuka-c mayuka-c deleted the add-revive-rules-part4 branch February 17, 2026 09:49
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 cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants