Describe the enhancement:
When using add_kubernetes_metadata we populate a lot of fields, some of them related with the controller of the pod, like :
kubernetes.deployment.name (implemented in #23610)
kubernetes.statefulset.name

It would be interesting to enrich the documents of pods belonging to daemonsets with something like kubernetes.daemonset.name

Describe a specific use case for the enhancement or feature:
Being able to create visualizations or filter logs based on the daemonset name.

Considering that there are other kinds of resources where this might be beneficial (jobs, cronjobs or even CRDs), a different approach could be storing the fields:

kubernetes.controller.kind: Values could be "Deployment", "StatefulSet", "DaemonSet", etc.
kubernetes.controller.name: the name of the resource controlling this pod (when applicable).

That change in the schema would also allow much flexible and powerful visualizations because having data of the same nature (who controls the pod) in different fields is challenging.

For your consideration ;)

cc: @ChrsMark