-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Verticalpodautoscaler Collector (VPA) #1790
Comments
I fully understand the argument to remove the VPA Collector, but it's not possible right now. The values from the vpa-recommender looks like this: ...
status:
conditions:
- lastTransitionTime: "2022-07-04T13:40:27Z"
status: "True"
type: RecommendationProvided
recommendation:
containerRecommendations:
- containerName: main
lowerBound:
cpu: 25m
memory: 262144k
target:
cpu: 25m
memory: 262144k
uncappedTarget:
cpu: 25m
memory: 262144k
upperBound:
cpu: 25m
memory: 262144k and the "25m" cant be converted to a value... will just result in this:
As I see it, either: |
/assign |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
As we have now an implementation to collect metrics from Custom Resources, we want to remove the VPA Collector in KSM v3.0
The text was updated successfully, but these errors were encountered: