Skip to content

Clarify the VPA's ability to traverse ownership chains#9480

Open
adrianmoisey wants to merge 1 commit intokubernetes:masterfrom
adrianmoisey:clearify-ownerref
Open

Clarify the VPA's ability to traverse ownership chains#9480
adrianmoisey wants to merge 1 commit intokubernetes:masterfrom
adrianmoisey:clearify-ownerref

Conversation

@adrianmoisey
Copy link
Copy Markdown
Member

What type of PR is this?

/kind cleanup
/kind documentation

What this PR does / why we need it:

Clarify the VPA's ability to traverse ownership chains
Also change names in tests a little to be clearer

My plan was to make a test that proved the current behaviour, but with our current testing framework that was a bit difficult.

Which issue(s) this PR fixes:

Relates to #9072

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

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


/cc iamzili

Also change names in tests a little to be clearer
@k8s-ci-robot k8s-ci-robot requested a review from iamzili April 12, 2026 18:34
@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. kind/documentation Categorizes issue or PR as related to documentation. area/vertical-pod-autoscaler approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 12, 2026
@adrianmoisey
Copy link
Copy Markdown
Member Author

/retest

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.

/lgtm
/hold
holding for @iamzili review

were specified manually.

> [!WARNING]
> VPA can only manage Pods that are directly owned by the targeted Custom Resource. It does not support indirect ownership (e.g., targeting a resource that owns another controller, which in turn owns the Pods).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can we also mentioned that we are currently working to find a solution?

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.

I don't really want to make promises about the future, I'd rather just say how it is.
If anyone is interested, they can go looking at issues

Comment on lines +62 to +65
"Foo": {
{Kind: "NotScalingResource", Name: "iCanNotScale", Group: "foo"},
{Kind: "ScalingResource", Name: "iCanScale", Group: "foo"},
},
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for this :)

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

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. 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/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants