Joachim comments

Results 89 comments of


                                            Joachim

Support in-place resource update feature for VPA

One more reason to have this as a separate enum value is that since `Auto` is the default value it shouldn't be experimental / alpha feature.

Support in-place resource update feature for VPA

Sadly ([source](https://github.com/kubernetes/kubernetes/pull/102884/#issuecomment-1324175261)): > This feature missed the extended deadline after code freeze and therefore will not make it into 1.26.

Add KEP: Control VPA eviction behavior based on scaling direction and resource

https://github.com/kubernetes/autoscaler/pull/4831#pullrequestreview-1099346882 > We still need someone to check the API. @mwielgus can you please take a look?

Allow running e2e tests as presubmits on GitHub

@mwielgus please take a look

Support in-place resource update feature for VPA

#4016 was opened earlier for the same thing, let's have one issue for tracking this

VPA: deleting VPA and recreate it, still gives some recommendation

/remove-lifecycle stale

VPA: deleting VPA and recreate it, still gives some recommendation

/remove-lifecycle rotten

VPA: deleting VPA and recreate it, still gives some recommendation

/lifecycle frozen

Support GitHub/Prow labeling for issue/PR triage

I like the idea of allowing people to tag issues.

Kubernetes VPA as recommender for resource specification estimation

>What are the factors VPA will be considering when its providing a recommended values. VPA bases it's recommendation on history of resource usage of containers in the target (often deployment)....