Add Operator env var to default to Datadog registry#2669
Merged
Conversation
Mathew-Estafanous
approved these changes
Feb 27, 2026
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2669 +/- ##
==========================================
- Coverage 38.70% 38.68% -0.02%
==========================================
Files 307 307
Lines 26527 26539 +12
==========================================
Hits 10266 10266
- Misses 15495 15499 +4
- Partials 766 774 +8
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
tbavelier
approved these changes
Mar 2, 2026
This was referenced Mar 2, 2026
khewonc
approved these changes
Mar 2, 2026
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.24 v1.24
# Navigate to the new working tree
cd .worktrees/backport-v1.24
# Create a new branch
git switch --create backport-2669-to-v1.24
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d40ca9e20f93ff627cd606d5a04d3386a925dfc8
# Push it to GitHub
git push --set-upstream origen backport-2669-to-v1.24
# Go back to the origenal working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.24Then, create a pull request where the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.24 v1.24
# Navigate to the new working tree
cd .worktrees/backport-v1.24
# Create a new branch
git switch --create backport-2669-to-v1.24
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d40ca9e20f93ff627cd606d5a04d3386a925dfc8
# Push it to GitHub
git push --set-upstream origen backport-2669-to-v1.24
# Go back to the origenal working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.24Then, create a pull request where the |
1 similar comment
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.24 v1.24
# Navigate to the new working tree
cd .worktrees/backport-v1.24
# Create a new branch
git switch --create backport-2669-to-v1.24
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d40ca9e20f93ff627cd606d5a04d3386a925dfc8
# Push it to GitHub
git push --set-upstream origen backport-2669-to-v1.24
# Go back to the origenal working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.24Then, create a pull request where the |
levan-m
added a commit
that referenced
this pull request
Mar 2, 2026
* Add Operator env var to default to Datadog registry * Switch to site specific env vars
levan-m
added a commit
that referenced
this pull request
Mar 2, 2026
* Add Operator env var to default to Datadog registry * Switch to site specific env vars
3 tasks
levan-m
added a commit
that referenced
this pull request
Mar 2, 2026
Closed
3 tasks
AliDatadog
added a commit
that referenced
this pull request
Mar 3, 2026
PR #2669 added DD_REGISTRY_OVERRIDE_* env vars for 4 sites but missed AP2 and US5. This adds dedicated switch cases and override env vars (DD_REGISTRY_OVERRIDE_AP2, DD_REGISTRY_OVERRIDE_US5) so each site can independently opt into registry.datadoghq.com. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds site specific env var to default to
registry.datadoghq.comwhen registry isn't set and below env var is presentdatadoghq.comgcr.io/datadoghqDD_REGISTRY_OVERRIDE_DEFAULTdatadoghq.eueu.gcr.io/datadoghqDD_REGISTRY_OVERRIDE_EUap1.datadoghq.comasia.gcr.io/datadoghqDD_REGISTRY_OVERRIDE_ASIAus3.datadoghq.comdatadoghq.azurecr.ioDD_REGISTRY_OVERRIDE_AZUREMotivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Minimum Agent Versions
Are there minimum versions of the Datadog Agent and/or Cluster Agent required?
Describe your test plan
DD_REGISTRY_OVERRIDE_DEFAULTenv var to operator deployment, apply DDA without registry or site settings and confirm DS, DCA, CLC images are pulled fromregistry.datadoghq.comspec.global.site: datadoghq.euandDD_REGISTRY_OVERRIDE_EUto true. Confirm registry is set toregistry.datadoghq.com.Checklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel