-
Notifications
You must be signed in to change notification settings - Fork 98
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
Support extra Orchestrator-Explorer configuration and clusterchecks #348
Conversation
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, documentation
2eea21d
to
eb3670e
Compare
@@ -428,7 +437,7 @@ func TestDefaultDatadogAgentSpecAgent(t *testing.T) { | |||
}, | |||
}, | |||
{ | |||
name: "sparse config", | |||
name: "agent spec sparse config", |
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.
I have renamed it because two tests had the same name.
internal *OrchestratorExplorerConfig | ||
name string | ||
orc *DatadogFeatures | ||
clustercheck bool |
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.
I have introduced the clustercheck
to keep the tests working as they were.
@@ -22,7 +22,7 @@ func IsValidDatadogAgent(spec *DatadogAgentSpec) error { | |||
} | |||
} | |||
|
|||
if spec.Agent.SystemProbe.CustomConfig != nil { | |||
if spec.Agent.SystemProbe != nil && spec.Agent.SystemProbe.CustomConfig != nil { |
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.
fix panic
Codecov Report
@@ Coverage Diff @@
## main #348 +/- ##
===========================================
+ Coverage 38.11% 64.37% +26.26%
===========================================
Files 63 62 -1
Lines 11237 6878 -4359
===========================================
+ Hits 4283 4428 +145
+ Misses 6647 2134 -4513
- Partials 307 316 +9
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
docs 👍
* Update DatadogAgent CRD to allow custom configuration for the Orchestrator-Explorer feature. * Create dedicated RBAC for the cluster-check-runners. * Fix several controllers issues.
eb3670e
to
07d9e8a
Compare
}) | ||
|
||
By("Activating OrchestratorExplorer", func() { | ||
By("Disabeling OrchestratorExplorer", func() { |
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.
nit disabling (also here)
@@ -169,16 +169,10 @@ var _ = Describe("DatadogAgent Controller", func() { | |||
}, nil) | |||
}) | |||
|
|||
By("Activating Process", func() { |
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.
why removing this test?
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.
I moved it after, and converted to "Disabling Process", because now since Orchestrator is enable by default, it means that process-agent is already running, so the By("Activating Process" )
was doing nothing.
What does this PR do?
Orchestrator-Explorer feature.
Motivation
Better support complex deployment with the Orchestrator-Explorer
scheduled as cluster-check
Additional Notes
N/A
Describe your test plan
Deploy the agent with the example
datadog-agent-orchestrator-custom-conf.yaml
.You can modify it a bit to remove the
spec.features.orchestratorExplorer.conf
section and see that the configuration is updated and the DCA is restarted... to
pick-up the new configuration