Possible conflict with pod autoscaler

[Vlaaaaaaad]

Hi,

First of all, thank you for the awesome project! Creating this issue to track this after the talk we had at Kubecon EU.

This may interact badly with the pod autoscaler. Say there is a schedule that scales down a deployment every weekend to 1 replica. It turns out that this weekend is actually a work weekend and people are developing and working on the cluster. The pod autoscaler wants to scale up to 5 replicas on some metric( say memory, or CPU or a custom metric such as number of requests), but the kube-start-stop is set to 1 replica. They may get in a fight( scale up to 5, scale down to 1, scale up to 5 and so on).

This was not tested at all and the default behavior is to scale down to 0 replicas which would likely eliminate such issues.