Skip to content
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

Closed
mrueg opened this issue Jul 19, 2022 · 4 comments · Fixed by #2017
Closed

Remove Verticalpodautoscaler Collector (VPA) #1790

mrueg opened this issue Jul 19, 2022 · 4 comments · Fixed by #2017
Assignees

Comments

@mrueg
Copy link
Member

mrueg commented Jul 19, 2022

As we have now an implementation to collect metrics from Custom Resources, we want to remove the VPA Collector in KSM v3.0

@ninlil
Copy link

ninlil commented Aug 26, 2022

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:

E0826 12:39:39.333864  925520 registry_factory.go:556] "kube_autoscaling_k8s_io_v1_verticalpodautoscaler_cpu_rec" err="[status,recommendation,containerRecommendations,0,target]: [cpu]: []: strconv.ParseFloat: parsing \"25m\": invalid syntax"

As I see it, either:
a) update the VPA Collector to apiVersion autoscaling.k8s.io/v1 (according to #1718 )
b) implement a parser/converter for values that can convert the measurement unit to a plain value.

@rexagod
Copy link
Member

rexagod commented Sep 15, 2022

/assign

@k8s-triage-robot
Copy link

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:

  • 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2022
@mrueg
Copy link
Member Author

mrueg commented Dec 18, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

5 participants