Expose add_resource_metadata for container and pods resources

[tetianakravchenko]

Signed-off-by: Tetiana Kravchenko tetiana.kravchenko@elastic.co

What does this PR do?

Add possibility to configure add_recourse_metadata for pod and container resources.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

Related issues

• Closes Expose add_recourse_metadata option to k8s package #2362

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-01-11T10:15:26.105+0000

• Duration: 31 min 46 sec

• Commit: 36afb1c

Test stats 🧪

Test	Results
Failed	0
Passed	116
Skipped	0
Total	116

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[MichaelKatsoulis]

@tetianakravchenko why did you add the add_resouce_metadata only in pod, container, state_pod and state_container ?

[tetianakravchenko]

@MichaelKatsoulis add_resource_metadata configuration does not affect other resources except pod, container and service. add_resource_metadata is only used for generating pod metadata - here, then those settings are used in GenerateK8s of pod k8s resource - https://github.com/elastic/beats/blob/master/libbeat/common/kubernetes/metadata/pod.go#L82-L124 , the same idea for container metadata - https://github.com/elastic/beats/blob/master/metricbeat/module/kubernetes/util/kubernetes.go#L193. Other resources (deployment, daemonset, etc) are using generic GenerateK8s.

[MichaelKatsoulis]

I don't think the word additionally is needed here because we already have the word add but I am not sure

[MichaelKatsoulis]

LGTM