Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
snvk2889 opened this issue Mar 15, 2024 · 0 comments

Comments

@snvk2889
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant