# Metricbeat not reporting on port 10255 anymore using latest kubernetes, how to use the secured port 10250?

**URL:** <https://discuss.elastic.co/t/metricbeat-not-reporting-on-port-10255-anymore-using-latest-kubernetes-how-to-use-the-secured-port-10250/153605>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [October 23, 2018, 1:14pm UTC](https://discuss.elastic.co/t/metricbeat-not-reporting-on-port-10255-anymore-using-latest-kubernetes-how-to-use-the-secured-port-10250/153605 "2018-10-23T13:14:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [October 23, 2018, 2:20pm UTC](https://discuss.elastic.co/t/metricbeat-not-reporting-on-port-10255-anymore-using-latest-kubernetes-how-to-use-the-secured-port-10250/153605/4 "2018-10-23T14:20:20Z")

</div>

Yes, probably you have to change `localhost` to the name of the node. In our default manifests we added the `NODE_NAME` env var for this. So if you [have it](https://github.com/elastic/beats/blob/master/deploy/kubernetes/metricbeat-kubernetes.yaml#L126-L129) reported, just switch to `${NODE_NAME}:10250`.

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-not-reporting-on-port-10255-anymore-using-latest-kubernetes-how-to-use-the-secured-port-10250/153605)._