<p>Some context: I have multiple cron jobs running daily, weekly, hourly and some of which require significant processing power.
I would like to add requests and limitations to these container cron pods to try and enable vertical scaling and ensure that the assigned node will have enough capacity when being initialized. This will prevent me from having to have multiple large node available at all times and also letting me modify how many crons I can run in parallel easily.
I would like to try and avoid timed scaling since the cron jobs processing time can increase as the application grows.</p>
<p><strong>Edit - Additional Information</strong> :
Currently I am using Digital Ocean and utilizing it's UI for cluster autoscaling. I have it working with HPA's on deployments but not crons. Adding limits to crons does not trigger cluster autoscaling to my knowledge.</p>
<p>I have tried to enable HPA scaling with the cron but with no success. Basically it just sits on a pending status signalling that there is insufficient CPU available and does not generate a new node.</p>
<p>Does HPA scaling work with cron job pods and is there a way to achieve the same type of scaling?</p>

<p>HPA is used to scale more pods when pod loads are high, but this won't increase the resources on your cluster.</p>
<p>I think you're looking for <a href="https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler" rel="nofollow noreferrer">cluster autoscaler</a> (works on AWS, GKE and Azure) and will increase cluster capacity when pods can't be scheduled.</p>
