Fix DNS lookup failure error for host URLs

[FedeBev]

• 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 (Seems to be not required for current tests)

This is a fix PR for #394 bug, feel free to suggest any other solution/idea.

Thanks

[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?

[cla-checker-service]

Author of the following commits did not sign a Contributor Agreement:
34e98ee

Please, read and sign the above mentioned agreement if you want to contribute to this project

[FedeBev]

CLA has now been signed.
Sorry, what I have to do now?

[pbecotte]

I wound up fixing this like this-

#439 (comment)

[FedeBev]

I wound up fixing this like this-

#439 (comment)

That could be a great solution!
Both solutions are valid and feasible in my opinion, maybe I cane make this options configurable through values file, what do you think?

[pbecotte]

I had an earlier PR that set this variable, you could resurrect it and trim it down to just this. Eventually I came to the conclusion that host networking was the easiest solution, but almost never the right one. That's not up to me though ;)

[jmlrt]

Hi @FedeBev,
This was already discussed a lot, host networking can be a great addition to this chart as long as it is optional and disabled by default.
You can also find an example in @pbecotte's Filebeat PR (this was disabled by default in 538af31).

[FedeBev]

Hi @jmlrt ,
hostNetwork and dnsPolicy options are now configurable through values.

In my opinion also @pbecotte solution is fine, but I can't see the new options in 7.6 release and in my opinion is needful.

Please, could you let me know the state on that?

Thanks

[jmlrt]

Hi @FedeBev, many thanks for this PR.
Sorry for the long delay for reviewing this PR.

Filebeat PR for hostNetwork (#321) use only hostNetworking value to manage both hostNetwork and dnsPolicy.

From what I see in Pod’s DNS Policy doc, the only relevant dnsPolicy values are ClusterFirst (default value) when hostNetwork is disabled and ClusterFirstWithHostNet when hostNetwork is enabled.

Do you have some use case where you would need a different policy?

[jmlrt]

@FedeBev I created #585 to add host networking to Metricbeat while staying consistent with Filebeat.
This will be merged today or in a couple of days so I'll close your PR.

I'm sorry for making you wait so long then replacing your work due to bad timing.
I hope it won't demotivate you for contributing to this repos in the future.

[FedeBev]

Hi @jmlrt, thank's for you work.

I kept the options separate to leave maximum configuration flexibility. At the moment I can't image a situation where this is really required, so it's perfectly fine for me to keep that configuration in one option and #585 is perfect for my use case.

Don't worry for the timing, luckily the workaround was very easy 😄