Update AEP-8026: Allow per-VPA component configuration parameters

[omerap12]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

Addressing #8012 (comment)

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

As I can see we can have OOM configuration at both VPA-level (using containerPolicy with "*") and container-level. While both approaches work technically, I would appreciate your thoughts on which approach is more appropriate. Currently, the proposal keeps it at container-level for consistency with other container policies, but I'm open to discussion.

Also note that oomBumpUp will be replacing the existing global configuration when specified in a VPA object - we can achieve the same capabilities with only one config value.

Does this PR introduce a user-facing change?

NONE

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

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: omerap12
Once this PR has been reviewed and has the lgtm label, please assign jackfrancis for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• vertical-pod-autoscaler/enhancements/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[omerap12]

/label tide/merge-method-squash

[adrianmoisey]

/retitle Update AEP-8026: Allow per-VPA component configuration parameters

[adrianmoisey]

This LGTM, but I believe it needs api-review

If you agree, can you add the label?

[omerap12]

This LGTM, but I believe it needs api-review

If you agree, can you add the label?

Thanks for the title fix :)
/label api-review