-
Couldn't load subscription status.
- Fork 128
Add helm metadata forwarder #2273
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2273 +/- ##
==========================================
- Coverage 38.05% 37.91% -0.14%
==========================================
Files 255 256 +1
Lines 20949 21207 +258
==========================================
+ Hits 7972 8041 +69
- Misses 12359 12544 +185
- Partials 618 622 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
What does this PR do?
pkg/util/metadatawhich extends fromSharedMetadataMotivation
https://datadoghq.atlassian.net/browse/AGENTONB-2594
We want to extend the current metadata forwarding schema in the Operator to also collect metadata on helm values configurations. This is necessary for future work in Agent Onboarding and Fleet Automation.
Additional Notes
Anything else we should know when reviewing?
Minimum Agent Versions
Are there minimum versions of the Datadog Agent and/or Cluster Agent required?
Describe your test plan
datadoganddatadog-operator)TBD: test on staging after EVWPR backend is implemented with feature flag
Checklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel