use host networking for filebeat so that the stats have the correct n…

[pbecotte]

…ode information

• Chart version not bumped (the versions are all bumped and released at the same time)
• README.md updated with any new values or changes
• Updated template tests in ${CHART}/tests/*.py
• Updated integration tests in ${CHART}/examples/*/test/goss.yaml

matches changes I made to metricbeat to get hostnames reporting properly on Digital Ocean

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[jmlrt]

jenkins test this please

[jmlrt]

⛴

[jmlrt]

Hi @pbecotte,
We got an issue with this PR and Filebeat 7.5.0. The fact is that enabling hostNetwork by default fail our tests in 7.5.0 (and even if tests are OK with 7.4.2, we are not in a good state as filebeat reported an error of pod already used but didn't fail).

We also have use cases where hostNetwork is not possible (OpenShift for example).

FYI we'll have to disable hostNetwork by default and allow enabling it in by setting hostNetworking=true.

[pbecotte]

As I mentioned, I am not an elastic stack expert, so if that's necessary that's great :) It is important to mention though, without these changes nothing actually worked on digital ocean. Everything came up, but the metrics were all using container names as hostnames and none of the server level metrics were aggregating.

Would just ask to check that the metrics all look right with the changed config before making any decisions. The code that the comments implied were supposed to fix that didn't seem to work, and I iterated on it for a while before resorting to this approach.

[jmlrt]

FYI HostNetwork was disabled by default in 538af31. In your case where you need it, you'll just need to set HostNetworking: true in your values.