# Metricbeat 7.17.7 generate a network overload on our Kubernetes nodes and API

**URL:** <https://discuss.elastic.co/t/metricbeat-7-17-7-generate-a-network-overload-on-our-kubernetes-nodes-and-api/317681>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [October 28, 2022, 12:12pm UTC](https://discuss.elastic.co/t/metricbeat-7-17-7-generate-a-network-overload-on-our-kubernetes-nodes-and-api/317681 "2022-10-28T12:12:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebglon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebglon/32/112637_2.png) [@sebglon](https://discuss.elastic.co/u/sebglon)\
**Post date:** [October 28, 2022, 12:12pm UTC](https://discuss.elastic.co/t/metricbeat-7-17-7-generate-a-network-overload-on-our-kubernetes-nodes-and-api/317681/1 "2022-10-28T12:12:02Z")

</div>

After upgrading from Metricbeat 7.10 to 7.17.7, we have a production outage due to network overload on our kubernetes nodes network and API.

After deleting the MetricBean daemonset, we have no more issue.  
We have not identified the root cause on the metricbeat config.

Have you already seen this behaviour?

K8S: v1.17  
Metricbeat: v7.17.7  
Elastic: 8.4

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 25, 2022, 2:12pm UTC](https://discuss.elastic.co/t/metricbeat-7-17-7-generate-a-network-overload-on-our-kubernetes-nodes-and-api/317681/2 "2022-11-25T14:12:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.