<p>Trying  to add autoscaling to my deployment,but getting   <code>ScalingActive  False</code>,most answers are about DNS,Heapster,Limits I've done all but still can't find solution.</p>

<pre><code>kubectl get hpa
NAME      REFERENCE          TARGETS         MINPODS   MAXPODS   REPLICAS   AGE
fetch     Deployment/fetch   &lt;unknown&gt;/50%   1         4         1          13m


kubectl cluster-info
Kubernetes master is running at --
addon-http-application-routing-default-http-backend is running at --
addon-http-application-routing-nginx-ingress is running at --
Heapster is running at  --
KubeDNS is running at --
kubernetes-dashboard is running at --
</code></pre>

<p>kubectl describe hpa`</p>

<p><a href="https://i.stack.imgur.com/8XpMN.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/8XpMN.png" alt="kubectl describe hpa"></a></p>

<p>yaml ` </p>

<p><a href="https://i.stack.imgur.com/4PS2U.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/4PS2U.png" alt="yaml"></a></p>

<p>PS.I tried to deploy example witch azure provides....getting the same,so yaml settings isn't problem </p>

<p>kubectl describe pod   `</p>

<p><a href="https://i.stack.imgur.com/N6Kt2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/N6Kt2.png" alt="undefined"></a></p>

<p>kubectl top pod fetch-54f697989d-wczvn --namespace=default` </p>

<p><a href="https://i.stack.imgur.com/S2mfy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/S2mfy.png" alt="enter image description here"></a></p>

<p>autoscaling by memory yaml `</p>

<p><a href="https://i.stack.imgur.com/5SxBO.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/5SxBO.png" alt="enter image description here"></a></p>

<p>description`</p>

<p><a href="https://i.stack.imgur.com/XLrnW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XLrnW.png" alt="enter image description here"></a></p>

<p><code>kubectl get hpa</code> give the same result,unknown/60%</p>

<p>I've experienced similar issues, my solutions are setting <code>resources.requests.cpu</code> section up in deployment config in order to calculate the current percentage based on the requested resource values. Your event log messages also means not to set up the request resource, but your deployment yaml seems no problem to me too.</p>

<p>Let we do double check as following steps.</p>

<p>If you can verify the resources as following cmd,</p>

<pre><code># kubectl top pod &lt;your pod name&gt; --namespace=&lt;your pod running namespace&gt;
</code></pre>

<p>And you would also need to check the pod requested cpu resources using below cmd in order to ensure same the config with your deployment yaml.</p>

<pre><code># kubectl describe pod &lt;your pod name&gt;
...
Requests:
  cpu:      250m
...
</code></pre>

<p>I hope it help you to resolve your issues. ;)</p>
