If I read the code correct, fields under _module should go on the module level. This means this would become kubernetes.namespace: default. This would also align well with https://github.com/elastic/beats/blob/master/libbeat/processors/add_kubernetes_metadata/_meta/fields.yml#L21

Please double check with data you receive when running 6.6. The same applies to all the other modules which use this labels magic.

Here is the magic I mentioned above. The part I don't know how you can access this label data below. You probably have to fetch it and delete the key and we change the "framework" later?

@exekias We seem to loose this field here but I would argue it's not an issue. WDYT?

Is this the kubernetes namespace? that field would be needed to identify the statefulset we are referring to

nevermind, I see this is a different namespace, we can drop it 👍

You'll see this "dropping field" pattern in more metricsets in Kubernetes. Just to give you some context @exekias the main idea was to achieve the migration, even dropping few things that weren't critical. In this case I have to admit that I was getting confused with the namespace thing (it seems there are 2 namespaces, the one of kubernetes and the other 😄 ) but I'd need to change quite a lot of code to test the module fields and the root fields (current code only tests metricset fields)

So, now that we have the new testing framework of @ruflin it seemed like the way to go and maybe delete current testing code if it doesn't achieve much more than what we get with the contents of testdata folder.

I know it seems confusing so just ping me if you need a longer explanation 😉

I think I got it, I'm ok with the change 👍