Skip to content

fix(acr): enable ADP check source when ACR is enable - #3471

Open
fabbing wants to merge 2 commits into
mainfrom
fabbing/checkrunner-adp-checks-pipeline
Open

fabbing wants to merge 2 commits into
mainfrom
fabbing/checkrunner-adp-checks-pipeline

Conversation

@fabbing

@fabbing fabbing commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Enable the ADP check source when ACR is enable.

Motivation

ACR forward checks events to ADP, without the ADP check source they aren't processed.

Additional Notes

Minimum Agent Versions

Are there minimum versions of the Datadog Agent and/or Cluster Agent required?

  • Agent: not released yet (dev build)

Describe your test plan

Checklist

  • PR has at least one valid label: bug, enhancement, refactoring, documentation, tooling, and/or dependencies
  • PR has a milestone or the qa/skip-qa label
  • All commits are signed (see: signing commits)

@fabbing
fabbing requested a review from a team September 16, 2026 13:45
@fabbing fabbing added bug Something isn't working qa/skip-qa labels Sep 16, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 95de9cf28c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +62 to +64
if !featureutils.IsDataPlaneEnabled(dda, ddaSpec, f.defaultDataPlaneEnabled) {
f.logger.Info("The checkrunner feature requires the dataPlane feature.")
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Require the data-plane component instead of only logging

When Check Runner is enabled while Data Plane remains at its default false or is explicitly disabled, this branch only emits a log and Configure still requires solely AgentCheckRunnerContainerName. The optimized pod therefore omits the agent-data-plane container; the later AddEnvVarToContainer call silently finds no target, while ACR continues sending to localhost:5105, leaving its checks unprocessed. Require/enable the Data Plane component here or reject this configuration rather than proceeding.

Useful? React with 👍 / 👎.

@datadog-prod-us1-6

datadog-prod-us1-6 Bot commented Sep 16, 2026

Copy link
Copy Markdown

Code Coverage

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 51.36% (+0.15%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: dec4ce0 | Docs | Give us feedback!

@tobz tobz left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a note about where ADP configurations should be placed, container-wise, to ensure the proper flow of configuration data.

Comment on lines +89 to +93
// ADP must serve the Checks IPC endpoint ACR is pointed at.
adpEnvVars := mgr.EnvVarMgr.EnvVarsByC[apicommon.AgentDataPlaneContainerName]
assert.Contains(t, adpEnvVars, dataPlaneChecksEnabledEnvVar, "DD_DATA_PLANE_CHECKS_ENABLED should be set on the agent data plane so it serves the Checks IPC source")
assert.NotContains(t, agentEnvVars, dataPlaneChecksEnabledEnvVar, "DD_DATA_PLANE_CHECKS_ENABLED is an ADP setting and should not be set on the core agent")

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We actually don't want to do this: the goal is that all configuration flows through the Core Agent, so we should set these configurations on the Core Agent directly.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good point! Addressed with: dec4ce0.
Then I got bitten by the config schema because it didn't know the keys!

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants