# 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:** 5

<div class="post-metadata">

### Author: ![pastorsx](https://avatars.discourse-cdn.com/v4/letter/p/58956e/32.png) [@pastorsx](https://discuss.elastic.co/u/pastorsx)
#### Post date: [October 23, 2018, 4:06pm UTC](https://discuss.elastic.co/t/metricbeat-not-reporting-on-port-10255-anymore-using-latest-kubernetes-how-to-use-the-secured-port-10250/153605/5 "2018-10-23T16:06:01Z")

</div>

yeah.. thanks, I tried that too... that's what I have, but still no luck (get the same x509 error):

kubernetes:  
enabled: true  
config:

- module: kubernetes  
metricsets:
- node
- system
- pod
- container
- volume  
period: 10s  
hosts: ["https://${HOSTNAME}:10250"]  
bearer\_token\_file: /var/run/secrets/kubernetes.io/serviceaccount/token  
ssl.certificate\_authorities:
- /var/run/secrets/kubernetes.io/serviceaccount/ca.crt  
add\_metadata: true  
in\_cluster: true

---

_[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)._