Skip to content

Use registry.datadoghq.com for Agent image defaults - #3098

Draft
AliDatadog wants to merge 1 commit into
mainfrom
ali.b/operator-registry-datadoghq
Draft

Use registry.datadoghq.com for Agent image defaults#3098
AliDatadog wants to merge 1 commit into
mainfrom
ali.b/operator-registry-datadoghq

Conversation

@AliDatadog

@AliDatadog AliDatadog commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

What

Change the Operator Agent image default registry from gcr.io/datadoghq to registry.datadoghq.com by pointing DefaultImageRegistry at the existing DatadogContainerRegistry constant.

This also updates generated DatadogAgent registry descriptions in CRD and bundle artifacts so the documented default matches the runtime default. GCR remains listed as the Google Container Registry option for explicit overrides.

Why

The public container registry guidance recommends registry.datadoghq.com as the simple/default Datadog registry while preserving cloud-provider registries for users who explicitly choose them. The Operator should generate default Agent, Cluster Agent, and DDOT image references from the same default registry.

Validation

  • make manifests
  • make bundle VERSION=1.27.0 refreshed the bundle registry descriptions before hack/patch-bundle.sh exited locally on an unbound LATEST_VERSION; unrelated generated bundle churn was pruned from the final diff.
  • go test ./internal/controller/datadogagent ./internal/controller/datadogagent/defaults ./pkg/images

@datadog-official

datadog-official Bot commented Jun 5, 2026

Copy link
Copy Markdown

Pipelines  Code Coverage

Fix all issues with BitsAI

⚠️ Warnings

🚦 3 Pipeline jobs failed

DataDog/datadog-operator | generate_code   View in Datadog   GitLab

pull request linter | Check Milestone   View in Datadog   GitHub Actions

pull request linter | build   View in Datadog   GitHub Actions

ℹ️ Info

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 44.10% (+0.11%)

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 57fc535 | Docs | Datadog PR Page | Give us feedback!

@AliDatadog
AliDatadog force-pushed the ali.b/operator-registry-datadoghq branch from 06b4049 to 57fc535 Compare June 8, 2026 09:20
@AliDatadog AliDatadog added the enhancement New feature or request label Jun 8, 2026 — with ddtool CLI
@codecov-commenter

codecov-commenter commented Jun 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.77%. Comparing base (39d6bd3) to head (57fc535).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #3098      +/-   ##
==========================================
+ Coverage   43.66%   43.77%   +0.11%     
==========================================
  Files         352      352              
  Lines       30115    30234     +119     
==========================================
+ Hits        13149    13235      +86     
- Misses      16094    16127      +33     
  Partials      872      872              
Flag Coverage Δ
unittests 43.77% <ø> (+0.11%) ⬆️

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

Files with missing lines Coverage Δ
pkg/images/images.go 97.34% <ø> (ø)

... and 3 files with indirect coverage changes


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 39d6bd3...57fc535. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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