-
Notifications
You must be signed in to change notification settings - Fork 110
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
Allow the ability to disable or specify custom host ports for OTLP #1440
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1440 +/- ##
==========================================
+ Coverage 48.89% 49.01% +0.12%
==========================================
Files 223 223
Lines 19455 19501 +46
==========================================
+ Hits 9513 9559 +46
Misses 9453 9453
Partials 489 489
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
776e22c
to
9e51951
Compare
Co-authored-by: khewonc <39867936+khewonc@users.noreply.github.com>
Signed-off-by: mrmcpat <patrick.liang@datadoghq.com>
Signed-off-by: mrmcpat <patrick.liang@datadoghq.com>
9e51951
to
ab16b05
Compare
What does this PR do?
Add the ability to disable host ports for OTLP and specify custom host ports.
Motivation
CECO-663
#903
Anything else we should know when reviewing?
N/A
Are there minimum versions of the Datadog Agent and/or Cluster Agent required?
N/A
Describe your test plan
Play around with the following DatadogAgent configuration:
Run
kubectl describe pod <node agent pod>
and see if the behavior reflects.For running the node agent in a single container:
Run
kubectl describe pod <node agent pod>
and see if the behavior reflects.Checklist
bug
,enhancement
,refactoring
,documentation
,tooling
, and/ordependencies
qa/skip-qa
label