VPA admission controller certificate is not reloaded

[bmendoza820]

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

What version of the component are you using?: 0.13.0

Component version: 0.13.0

What k8s version are you using (kubectl version)?: 1.24

kubectl version Output

$ kubectl version

What environment is this in?: AWS EKS

What did you expect to happen?: When using cert-manager to generate the secret containing TLS certs for the VPA admission controller, updates to the secret should trigger a reload so that the VPA admission controller is still available.

What happened instead?: When using cert-manager to generate the secret containing TLS certs for the VPA admission controller, updates to the secret result in the VPA admission controller reporting a bad certificate.

How to reproduce it (as minimally and precisely as possible): See above

Anything else we need to know?:

Re-filing this as a +1 to #3458.
I see that #3462 was opened but eventually closed.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[itspngu]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[itspngu]

/remove-lifecycle stale

[voelzmo]

Will be fixed by #6665