pprof for vpa-admission-controller

[huizhifan]

Which component are you using?:
vertical-pod-autoscaler

vpa-admission-controller
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

In our cluster, there are 3k pods and 100-200 vpa objects with Off updateMode. Theoretically, the vpa-admission-controller is supposed to have little work load. But the memory usage goes up to 1000Mi. We want to learn why this amount of memory is consue
Describe the solution you'd like.:

Enable pprof in vpa-admission-controller
Describe any alternative solutions you've considered.:

Additional context.:

[adrianmoisey]

/area vertical-pod-autoscaler

[voelzmo]

/triage accepted
/label good-first-issue

This is very relevant to issues we've seen before like #6368

[k8s-ci-robot]

@voelzmo: The label(s) `/label good-first-issue

cannot be applied. These labels are supported:api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labelsorlabels -> restricted_labelsinplugin.yaml`?

In response to this:

/triage accepted
/label good-first-issue

This is very relevant to issues we've seen before like #6368

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.

[voelzmo]

/label good first issue

[voelzmo]

/label "good first issue"

[voelzmo]

/assign @adrianmoisey

[raywainman]

/good-first-issue

[k8s-ci-robot]

@raywainman:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.