Cherry-pick of PR #23610 to 7.x branch. Original message:

What does this PR do?

This PR adds kubernetes.deployment.name in Pods' metadata. Right now we only add kubernetes.replicaset.name when a Pod is handled by a Deployment since a Deployment controls the Pod through a ReplicaSet and the ReplicaSet is considered as the direct owner of the Pod in k8s API. In this we need an extra step check to retrieve the owner of the ReplicaSet if possible.

Why is it important?

So as to correlate Pods with Deployments controlling them.

How to test this PR locally

1. Deploy a sample Deployment on k8s: kubectl apply -f https://k8s.io/examples/controllers/nginx-deployment.yaml
2. Deploy Metricbeat (instructions) on k8s and verify that events shiped by pod and state_pod metricset include kubernetes.deployment.name when kubernetes.replicaset.name exists. As an example see screenshots below.

Extra: Verify that add_kubernetes_metadata adds kubernetes.deployment.name when kubernetes.replicaset.name exists, using the following configuration with Filebeat on k8s:

filebeat.inputs:
- type: container
  paths:
    - /var/log/containers/*.log
  processors:
    - add_kubernetes_metadata:
        host: ${NODE_NAME}
        matchers:
        - logs_path:
            logs_path: "/var/log/containers/"

Related issues

• Closes Add metadata of deployment controlling pods #20991

Screenshots