# Why does Helm chart for netdata-child daemonset use hostNetwork?

**URL:** <https://community.netdata.cloud/t/why-does-helm-chart-for-netdata-child-daemonset-use-hostnetwork/749>\
**Category:** Help\
**Tags:** agent-collector, kubernetes, agent\
**Created:** [January 11, 2021, 9:24am UTC](https://community.netdata.cloud/t/why-does-helm-chart-for-netdata-child-daemonset-use-hostnetwork/749 "2021-01-11T09:24:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sdo](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/sdo/32/360_2.png) [@sdo](https://community.netdata.cloud/u/sdo)\
**Post date:** [January 11, 2021, 9:24am UTC](https://community.netdata.cloud/t/why-does-helm-chart-for-netdata-child-daemonset-use-hostnetwork/749/1 "2021-01-11T09:24:19Z")

</div>

## Environment

Kubernetes

## Problem/Question

Question

## What I expected to happen

[https://github.com/netdata/helmchart/blob/master/charts/netdata/templates/daemonset.yaml#L43](https://github.com/netdata/helmchart/blob/master/charts/netdata/templates/daemonset.yaml#L43) shows that pods are using hostNetwork and exposing port 19999 externally.

Why is this necessary?

Given that daemonset streams data to netdata-parent deployment, my expectation is that hostNetwork is not necessary, and also netdata-child pods should not need to have any ports open.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [January 12, 2021, 8:19am UTC](https://community.netdata.cloud/t/why-does-helm-chart-for-netdata-child-daemonset-use-hostnetwork/749/2 "2021-01-12T08:19:34Z")

</div>

Hi @sdo.

You are right, netdata child (daemonset) manifest has `hostNetwork: true` and it is [not user configurable](https://github.com/netdata/helmchart/blob/33fc823fe4650d64c1483a39b273e1d5430f77e2/charts/netdata/templates/daemonset.yaml#L43), so it is hard requirement.

Check [the issue where we discussed it](https://github.com/netdata/helmchart/pull/96). One of the reasons - we want to be able to collect data from the applications listening on localhost. For example - kubelet (not containerized), but it can be done via [api server proxy feature](https://github.com/netdata/helmchart/pull/96#issuecomment-624671392). Likely there are other things i didn’t mention.

What we need to do is to make clear why we need `hostNetwork: true` and make it user configurable, i agree.