Inconsistent behaviour within VPA components regarding targetRef #6924
Labels
area/vertical-pod-autoscaler
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Which component are you using?:
vertical-pod-autoscaler
What version of the component are you using?:
Component version: 1.1.2
What k8s version are you using (
kubectl version
)?:Various: 1.28 and 1.30
What environment is this in?:
Any. I've reproduced in GKE, AWS (kOps) and Kind.
What did you expect to happen?:
When setting a targetRef with a lowecase
kind
, the VPA admission-controller doesn't match the new Pods.However, the updater component does match the Pod.
What happened instead?:
Pod wasn't matched in the admission-controller
How to reproduce it (as minimally and precisely as possible):
Use the hamster example in this repo, and replace "Deployment" with "deployment"
Anything else we need to know?:
deployment
/area vertical-pod-autoscaler
/assign
The text was updated successfully, but these errors were encountered: