autoscaler icon indicating copy to clipboard operation
autoscaler copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Support for different TargetCPUPercentiles through alternative recommender

Open jbartosik opened this issue 3 years ago • 4 comments

It would be nice if one could choose to use different percentiles as base for VPA recommendation. We can do that by:

  1. Adding flags so one can run VPA recommender that sets recommendations on VPA Objects with a specified name. (and also if it should set recommendation for VPA objects that don't specify which recommender should generate recommendation for them)

Currently VPA recommender sets recommendations for VPAs which (source):

  • don't specify which recommender they use or
  • are explicitly configured to use default recommender.
  1. Adding flags so one can change target CPU percentiles.
  2. Adding instruction on how to run two recommenders with different configuration in one cluster.

I'll check if it's feasible to add e2e test for running two VPA recommenders at the same time.

jbartosik avatar Apr 05 '22 14:04 jbartosik

/assign

matthyx avatar Apr 06 '22 08:04 matthyx

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-triage-robot avatar Jul 05 '22 09:07 k8s-triage-robot

The Kubernetes project currently lacks enough active 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 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 rotten

k8s-triage-robot avatar Aug 04 '22 10:08 k8s-triage-robot

/remove-lifecycle rotten

matthyx avatar Aug 04 '22 11:08 matthyx