-
Notifications
You must be signed in to change notification settings - Fork 148
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
[backport 8.10] Elastic-agent-autodiscover to v0.6.4 #3591
Conversation
🌐 Coverage report
|
@cmacknz can I merge this as only vulncheck fails? |
/test |
We just removed the govulncheck #3596 |
/test |
@pierrehilbert, @cmacknz I have retried the test but still fails. It is the elastic-agent build so I am reluctant to merge. Can you have a look please? |
/test |
Looks good to go this time. |
Can you please make it at least configurable? We use |
What does this PR do?
WHAT: Update the Elastic-agent-autodiscover to v0.6.4. This disables by default metadata enrichment for deployment and cronjobs
WHY: The metadata enrichemnt for replicasets (which are produced from deployments) and cronjobs is proved a feature with heavy memory usage especially in big kubernetes clusters. The outcome was to enhance pods that were created from deployments and cronjobs with the relevant deployment/cronjob name. Decision
Why is it important?
We want to avoid the memory impact of keeping the feature enabled in big k8s clusters
Checklist
./changelog/fragments
using the changelog toolRelated issues