# 'kubectl top' and Horizontal Pod Autoscalers Don't Work

**URL:** <https://community.replicated.com/t/kubectl-top-and-horizontal-pod-autoscalers-dont-work/467>\
**Category:** Supporting your customers\
**Created:** [November 6, 2020, 5:31pm UTC](https://community.replicated.com/t/kubectl-top-and-horizontal-pod-autoscalers-dont-work/467 "2020-11-06T17:31:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikogura](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/nikogura/32/320_2.png) [@nikogura](https://community.replicated.com/u/nikogura)\
**Post date:** [November 6, 2020, 5:31pm UTC](https://community.replicated.com/t/kubectl-top-and-horizontal-pod-autoscalers-dont-work/467/1 "2020-11-06T17:31:40Z")

</div>

When using kURL with Metrics Server, if you happen to install into an environment where you don’t have full blown DNS set up, metrics will not be accessible, and HPA’s will not function.

The solution is to run `kubectl edit deploy metrics-server -n kube-system` and add the following to the args:

```
- --kubelet-preferred-address-types=InternalIP

```

Save that, and wait a few minutes, and the metrics will flow.
