Closed rkashasl closed 4 months ago
Same issue here. It looks like that VPA recommender actually is broken, no recommendations are applied to new VPAs
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Without additional information, I assume that this is another instance of https://github.com/kubernetes/autoscaler/issues/6744 which could be fixed with https://github.com/kubernetes/autoscaler/pull/6745
TL;DR: stale recommendations that don't have a matching Pod anymore can exist, when you e.g. renamed a Container in a Pod.
I'm closing this in favor of the above mentioned issue. Feel free to re-open with additional information.
/close
@voelzmo: Closing this issue.
Hello! We are using latest vpa chart:
However we see an errors about cert-manager container that vpa-updater pod spamming:
Here is a cer-manager deployment and it's vpa:
And there is no cert-manager container name it refers to in deployment: