Cherry-pick #16554 to 7.x: Fix k8s pod annotations tier in metadata #16580
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #16554 to 7.x branch. Original message:
Follow-up of #16480 PR.
It was found also that
kubernetes.annotations.*
do not follow the schema defined atbeats/libbeat/processors/add_kubernetes_metadata/_meta/fields.yml
Line 38 in 2e4d292
This PR aims to fix it.
Not sure if we should fix it in general for all resources at
beats/libbeat/common/kubernetes/metadata/resource.go
Line 105 in dba8f74