Add .* to kubernetes labels and annotations in fields.yml mapping

[kaiyan-sheng]

This PR is to fix mapping for kubernetes.labels and kubernetes.annotations in fields.yml. The error message is caused by this look like:

{"type":"mapper_parsing_exception","reason":"object mapping for [kubernetes.labels.app] tried to parse field [app] as object, but found a concrete value"}

closes #12638

[jsoriano]

I thought that .* was appended if needed but it seems that it isn't.

I am ok with adding the wildcard explicitly in any case, once tests pass.

[kaiyan-sheng]

@jsoriano Thanks! What do you think about backporting this?

[jsoriano]

@jsoriano Thanks! What do you think about backporting this?

It can be a good idea, it will surely do more good than harm.

[glaenen]

Still seeing this issue with Metricbeat 7.6.0

{"type":"mapper_parsing_exception","reason":"failed to parse field [kubernetes.labels.statefulset] of type [keyword] in document with id 'HPFwzXABACATvuNpI5wp'. Preview of field's value: '{kubernetes={io/pod-name=elastic-es-hot-0}}'","caused_by":{"type":"illegal_state_exception","reason":"Can't get text on a START_OBJECT at 1:122"}}

[jsoriano]

Still seeing this issue with Metricbeat 7.6.0

{"type":"mapper_parsing_exception","reason":"failed to parse field [kubernetes.labels.statefulset] of type [keyword] in document with id 'HPFwzXABACATvuNpI5wp'. Preview of field's value: '{kubernetes={io/pod-name=elastic-es-hot-0}}'","caused_by":{"type":"illegal_state_exception","reason":"Can't get text on a START_OBJECT at 1:122"}}

This issue should be fixed by #16834, that will be released in 7.6.2.