split some of the deployment and daemonset config to make things more…

[pbecotte]

… flexible

• 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

Looking at #446 realized we may want to split daemonset/deployment config in some places. This is kind of a big change to the values file though, so not sure if theres a better way to transition. Consider this as a proposal :)

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

[FedeBev]

I agree with you: this is a big change. However I can't a better way to do that.

Thanks

[jmlrt]

jenkins test this please

[mitchellmaler]

Can this PR be merged in? We are still having issues with the resources being the same on all pods even though the daemonset pods use much less compared to the deployment pod.

[jmlrt]

Hey @pbecotte,
Thanks for your PR, however, this is a breaking change and we'd like to ensure user with old values can still use the chart after splitting config, so I started a rework in #572, which should allow re-using old values if they are still used.

[jmlrt]

Closed by #572
Thanks for your work @pbecotte