<p>I am running a Kubernetes cluster v1.16(currently newest version on GKE) with HPA that scales the deployments base on custom metrics(Specifically rabbitmq messages count fetched from google cloud monitoring).</p>
<p><strong>The Problem</strong></p>
<p>The deployments scale up very fast to maximum pod count when the message count is temporarily high.</p>
<p><strong>Information</strong></p>
<p>The HPA --horizontal-pod-autoscaler-sync-period is set to 15 seconds on GKE and can't be changed as far as I know.</p>
<p>My custom metrics are updated every 30 seconds.</p>
<p>I believe that what causes this behavior is that when there is a high message count in the queues every 15 seconds the HPA triggers a scale up and after few cycles it reaches maximum pod capacity.</p>
<p>In kubernetes api v1.18 you can control scale up stabilization time, but I can't find a similar feature in v1.16.</p>
<p><strong>My Question</strong></p>
<p>How can I make the HPA scale up more gradually?</p>
<p><strong>Edit 1</strong></p>
<p>Sample HPA of one of my deployments:</p>
<pre><code>apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: my-deployment-hpa
  namespace: production
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: my-deployment
  minReplicas: 6
  maxReplicas: 100
  metrics:
  - type: External
    external:
      metricName: &quot;custom.googleapis.com|rabbit_mq|v1-compare|messages_count&quot;
      metricSelector:
        matchLabels:
          metric.labels.name: production
      targetValue: 500
  
</code></pre>

<p>First, a good piece of information to know, is that there is a built-in cooldown in Kubernetes for autoscalers. Quoting from Kubernetes in Action:</p>
<blockquote>
<p>Currently,  a  scale-up  will  occur  only  if  no  rescaling event occurred in the last three minutes. A scale-down event is performed even less frequently—every  five  minutes.  Keep  this  in  mind  so  you  don’t  wonder  why  the autoscaler  refuses  to  perform  a  rescale  operation  even  if  the  metrics  clearly  showthat it should.</p>
</blockquote>
<p>It might be that this statement is outdated, but unless it changed, this is hardcoded, and each scale up/down event should not scale more that 100% of existing pods.</p>
<p>That said, you're not out of options either way, here are some approaches you can take:</p>
<ol>
<li><strong>Pass your custom metric for scaling through a time average function</strong> - last time I did this was using prometheus and promql might be different than what you are using, but if you share more configuration in your question, I'm sure I could help find the syntax.</li>
<li><strong>You can try using <a href="https://keda.sh/docs/2.0/scalers/rabbitmq-queue/" rel="noreferrer">Keda</a></strong> - It has a <code>cooldownPeriod</code> object that you can place in the <code>ScaledObject</code> custom resource it comes with.</li>
</ol>
