vpa "auto" mode does not work with replicas: 1

[suhas184]

The vpa hamster example in the git repo does not work if the replica count is decreased to 1 .

The deployment object definition is as below:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: hamster
spec:
replicas: 2

if we change the replicas to , it doesn't evict the pod and creare a new one with recommended cpu and memory. The recommendation is provided but it does not automatically recreate a pod with new specifications under "Auto" or "Recreate" mode.

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: hamster
spec:
replicas: 1

has anyone faced this issue before or is it a known behavior?

[mfilotto]

This is the expected comportment.
The updater is by default configured to apply changes only with a min of 2 replicas

https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/pkg/updater/main.go#L42

Till now I think we cannot change default parameters of Docker images, an issue is open about that concern
#1664

[bskiba]

@mfilotto is right, by default VPA will not evict pods if there are less than 2 replicas. Closing as configuring this will be possible once #1664 is addressed.
/close

[k8s-ci-robot]

@bskiba: Closing this issue.

In response to this:

@mfilotto is right, by default VPA will not evict pods if there are less than 2 replicas. Closing as configuring this will be possible once #1664 is addressed.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Sudhanshu-Saurav]

what happened to this issue is this resolved ?