-
Notifications
You must be signed in to change notification settings - Fork 113
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
Created a Datadog Agent Operator config file that allows the Datadog Agent as an Operator to work behind a proxy server #532
base: main
Are you sure you want to change the base?
Conversation
…luster behind a proxy server
…atadog Agent Examples subfolder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request does not contain a valid label. Please add one of the following labels: bug, enhancement, refactoring, documentation, tooling
Codecov Report
@@ Coverage Diff @@
## main #532 +/- ##
=======================================
Coverage 58.51% 58.51%
=======================================
Files 3 3
Lines 135 135
=======================================
Hits 79 79
Misses 43 43
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Addressing issue: DataDog#532 (comment) Co-authored-by: Ursula Chen <[email protected]>
Anything ever happen of this? I need this feature in my cluster. |
What does this PR do?
I have created a Datadog Agent file that allows the Datadog Agent as an Operator to work behind a proxy server
Motivation
IHAC that requires Datadog Agent as an Operator to work behind a proxy server
Additional Notes
I also included instructions in the Getting Started guide that helps in the setup of the Operator in order for it to work behind a proxy server
Describe your test plan
Tests can be conducted on any Kubernetes cluster