Closed szegedi closed 2 months ago
Run ID: 7584aa4d-b07d-41ef-80f6-853130a1ba4f Metrics dashboard Target profiles
Baseline: c7e91281df20bf43b47de56e1d16cc889da1bcb4 Comparison: 8855e1b2daf00f016e3e2a834bf7ec04c879738d
Performance changes are noted in the perf column of each table:
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
Use this command from test-infra-definitions to manually test this PR changes on a VM:
inv create-vm --pipeline-id=38725070 --os-family=ubuntu
Note: This applies to commit 8855e1b2
Thanks for the suggestion @adel121! There's currently an e2e onboarding system tests draft PR that exercises this functionality (with the drawback that it can only run tests for a released agent.) I'm glad to see that there's an AWS/Pulumi framework locally in the agent as well. I learned since from @robertomonteromiguel that folks that created agent's e2e have helped him create the onboarding system tests infrastructure too. I'll figure out how to validate the feature in this e2e framework and follow up with a test.
/merge
:steam_locomotive: MergeQueue: pull request added to the queue
The median merge time in main
is 32m.
Use /merge -c
to cancel this operation!
What does this PR do?
Allows Continuous Profiler to be enabled (or disabled) by Helm Charts config on the controller pod. The cluster-agent, running on the controller pod, will read an environment variable and use this to mutate the configuration of other pods to set the environment variables that will activate profiling within the tracer/profiler client libraries.
This PR follows the same approach as #23618 did for activation of ASM products.
Motivation
to make it easier for k8s clients to activate Continous Profiling. Simplified installation is a common request.
Additional Notes
The PR is designed to establish the fundamentals that will make these other PRs work:
Continuous Profiler will have the env var
DD_ADMISSION_CONTROLLER_AUTO_INSTRUMENTATION_APPSEC_ENABLED
set by changes in those Datadog Operator and Helm Charts PRs. It will result inDD_PROFILING_ENABLED
being propagated to all pods (or those conforming to the filters).Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
invoke test --targets=./pkg/clusteragent