k8s Metadata TODOs for v8.0.0

[ChrsMark]

This issue aims to keep track of changes that should be applied on metadata Generators for all the different resources.

Final decision was taken in #16558

• Namespace metadata Generator (

  beats/libbeat/common/kubernetes/metadata/namespace.go

  Line 50 in 9375fb9

  // TODO: remove this call when moving to 8.0

  ) PR: Move labels and annotations under kubernetes.namespace. #27917
  Convert kubernetes.namespace into an object: namespace -> namespace.name, namespace_uid -> namespace.uid, namespace_labels -> namespace.labels
• Pod metadata Generator (still in wip, see Fix k8s pod labels tier in metadata #16480)
• Handle namespaces' changes accordingly in Agent's k8s provider:

  beats/x-pack/elastic-agent/pkg/composable/providers/kubernetes/pod.go

  Line 221 in 46d17b4

  k8sMapping["namespace_annotations"] = namespaceAnnotations

  PR:Breaking change for 8.0, namespace_annotations replaced by namespace.annotations #28230
• Apply changes accordingly to kubernetes package in integration repository PR: Update kubernetes namespace field. breaking change integrations#1792

cc: @exekias @vjsamuel

ps: assigning this to myself so as not to get forgotten :)

[exekias]

I'm not quite convinced about moving pod labels to kubernetes.pod.labels. In general, having labels under a common place allow for correlation. For instance, give me all resources with label env: production. We should come up with a plan about this

[ChrsMark]

I'm not quite convinced about moving pod labels to kubernetes.pod.labels. In general, having labels under a common place allow for correlation. For instance, give me all resources with label env: production. We should come up with a plan about this

Plan was discussed and defined at #16558

[ChrsMark]

@MichaelKatsoulis I guess we are ok to close this one?

[MichaelKatsoulis]

Yes I will close that!