ci: build OTel operator images

[dineshg13]

What does this PR do?

Enables the libdatadogbuild OpenTelemetry Operator-compatible image jobs for Node.js. The repository already pins one-pipeline 1.5.0, so this adds only the feature flag and the nodejs language profile.

Motivation

Build dd-trace-js images that can be used directly with the OpenTelemetry Operator, matching the rollout in the Java and Python tracers.

Testing

• git diff --check
• The PR pipeline validates the generated one-pipeline image jobs.

No runtime tests are needed because this changes only GitLab CI variables.

Additional Notes

Equivalent to DataDog/dd-trace-java#12255 and DataDog/dd-trace-py#20239.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-10T17:29:08.350150Z	114f68d	PR opened
🔒 Security Review	✅ Completed 2026-09-10T17:31:47.492759Z	114f68d	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[dd-octo-sts]

Overall package size

Self size: 8.88 MB
Deduped: 9.55 MB
No deduping: 9.55 MB

Dependency sizes

| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.4.0 | 127.33 kB | 447.04 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |

_{🤖 This report was automatically generated by heaviest-objects-in-the-universe}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.69%. Comparing base (1c48f59) to head (114f68d).

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10278   +/-   ##
=======================================
  Coverage   98.69%   98.69%           
=======================================
  Files        1008     1008           
  Lines      158514   158514           
  Branches       74       74           
=======================================
  Hits       156448   156448           
  Misses       2066     2066           

Flag	Coverage Δ
ai-guard	65.20% <ø> (-0.02%)	⬇️
apm-capabilities	63.71% <ø> (+0.05%)	⬆️
apm-integrations	81.48% <ø> (-0.02%)	⬇️
appsec	58.90% <ø> (-0.01%)	⬇️
debugger	69.83% <ø> (-0.03%)	⬇️
instrumentation	53.89% <ø> (-0.01%)	⬇️
llmobs	79.11% <ø> (-0.02%)	⬇️
master-coverage	98.69% <ø> (?)
openfeature	66.42% <ø> (-0.02%)	⬇️
platform	69.33% <ø> (-0.01%)	⬇️
profiling	66.77% <ø> (-0.03%)	⬇️
serverless	65.74% <ø> (-0.02%)	⬇️
test-optimization	82.60% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[datadog-prod-us1-6]

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 98.17% (-0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 114f68d | Docs | View more details | Give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-10 17:40:34

Comparing candidate commit 114f68d in PR branch dinesh.gurumurthy/add-otel-operator-image with baseline commit 1c48f59 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 2305 metrics, 8 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:debugger-line-probe-with-snapshot-default-26

• unstable max_rss_usage [-9.842MB; +15.877MB] or [-4.195%; +6.767%]

scenario:encoders-0.4-immediate-flush-20

• unstable max_rss_usage [-8495.273KB; +8696.987KB] or [-11.093%; +11.356%]

scenario:llmobs-encode-unicode-mixed-20

• unstable max_rss_usage [-6.240MB; +12.622MB] or [-8.509%; +17.213%]

scenario:plugin-couchbase-upsert-24

• unstable cpu_user_time [-186.067ms; +288.864ms] or [-4.103%; +6.370%]
• unstable execution_time [-185.219ms; +290.706ms] or [-4.078%; +6.401%]

scenario:plugin-graphql-long-with-depth-off-26

• unstable max_rss_usage [-13.646MB; +21.306MB] or [-7.222%; +11.276%]

scenario:plugin-mongodb-core-binary-hash-24

• unstable execution_time [-176.223ms; +210.516ms] or [-6.000%; +7.168%]
• unstable throughput [-83412.837op/s; +74787.706op/s] or [-5.404%; +4.845%]