Open
Conversation
Codecov Report❌ Patch coverage is ❌ Your patch status has failed because the patch coverage (58.66%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #2501 +/- ##
==========================================
- Coverage 38.38% 38.37% -0.01%
==========================================
Files 300 300
Lines 25555 25569 +14
==========================================
+ Hits 9809 9813 +4
- Misses 15002 15010 +8
- Partials 744 746 +2
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:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Refactors shared Metadata:
sharedMetadataintosharedMetadataandbaseForwarderclusterIDonce at startup, and do not start the metadata forwarder if this step fails (the metadata cannot be used by FA without cluster ID)kube-systemnamespace to satisfy updated clusterId fetching mechanismMotivation
What inspired you to submit this pull request?
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
Noop -- this is a refactor PR so there should be no change in functionality. Tested on
abrahttps://github.com/DataDog/k8s-datadog-agent-ops/pull/7185 and confirmed that metadata for operator, helm and CRDs are being collected.Checklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel