Differences in the breaking change page for Kubernetes Autodiscover of all Beats

[snvk2889]

Problem:

I have noticed that there are differences in the breaking change page for Kubernetes Autodiscover of all Beats with the documentation we have publicly.

Affected Version : 8.11

In v8.11.0, a breaking change was introduced mentioned in below link that disables the collection of the fields kubernetes.deployment and kubernetes.cronjob by default to save some memory.
Changelog page - https://www.elastic.co/guide/en/beats/libbeat/current/release-notes-8.11.0.html#:~:text=Pods%20that%20will%20be%20created%20from%20deployments%20or%20cronjobs%20will%20not%20have%20the%20extra%20metadata%20field%20for%20kubernetes.deployment%20or%20kubernetes.cronjob%2C%20respectively.%2036879

However in the below Documentations for Filebeat and Heartbeat we can see that these metadata's will be applied as default

• https://www.elastic.co/guide/en/beats/filebeat/8.11/add-kubernetes-metadata.html#add-kubernetes-metadata:~:text=enabled%3A%20false.-,deployment,-%3A%20If%20resource%20is

• https://www.elastic.co/guide/en/beats/heartbeat/8.11/configuration-autodiscover.html#_kubernetes:~:text=enabled%3A%20false.-,deployment,-%3A%20If%20resource%20is

[eedugon]

Transferring the issue to beats repo.
@bmorelli25 , @kilfoyle , who owns beats docs?

I've just found this reported issue. I'm going to check if it's still an issue, as I'm familiar with the bug that caused that breaking change (#33307).

[bmorelli25]

who owns beats docs?

Technically the ingest team. But in reality no one as docs improvements have been deprioritized. If you think this is important to fix, we can prioritize it at assign it to you 😄.