I have Kuberenetes cluster hosted in Google Cloud.

I deployed my deployment and added an hpa rule for scaling.

kubectl autoscale deployment MY_DEP --max 10 --min 6 --cpu-percent 60

waiting a minute and run kubectl get hpa command to verify my scale rule - As expected, I have 6 pods running (according to min parameter).

$ kubectl get hpa
NAME                    REFERENCE                          TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
MY_DEP                  Deployment/MY_DEP                  <unknown>/60%   6         10        6          1m

Now, I want to change the min parameter:

kubectl patch hpa MY_DEP -p '{"spec":{"minReplicas": 1}}'

Wait for 30 minutes and run the command:

$ kubectl get hpa
NAME                    REFERENCE                          TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
MY_DEP                  Deployment/MY_DEP                  <unknown>/60%   1         10        6          30m

expected replicas: 1, actual replicas: 6

More information:

1. You can assume that the system has no computing anything (0% CPU utilization).
2. I waited for more than an hour. Nothing changed.
3. The same behavior is seen when i deleted the scaling rule and deployed it again. The replicas parameter has not changed.

Question:

If I changed the MINPODS parameter to "1" - why I still have 6 pods? How to make Kubernetes to actually change the min pods in my deployment?