Update Agent registry documentation defaults#36536
Conversation
github-actions
Bot
added
Architecture
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e22b4e3f34
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6773b49583
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5428a84193
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Kubernetes with the Datadog Operator | ||
|
|
||
| As of Operator chart version 2.19.0, the Datadog Operator is migrating to `registry.datadoghq.com` for both the operator image and Agent images it manages. Previously, Agent images were pulled from site-specific registries (`gcr.io/datadoghq`, `eu.gcr.io/datadoghq`, `asia.gcr.io/datadoghq`, or `datadoghq.azurecr.io`). To keep using the previous site-specific registries, set `registryMigrationMode: ""` in your Operator Helm `values.yaml`. | ||
| As of Datadog Operator chart version 2.19.0, when the Operator is installed through the Datadog Agent Helm chart dependency, the Datadog Agent Helm chart's `registryMigrationMode` can use `registry.datadoghq.com` for Agent images managed by the Operator. Earlier versions pulled Agent images from site-specific registries (`gcr.io/datadoghq`, `eu.gcr.io/datadoghq`, `asia.gcr.io/datadoghq`, or `datadoghq.azurecr.io`). To use the previous site-specific registries for Agent images in this deployment path, set `registryMigrationMode: ""` in your Datadog Agent Helm chart `values.yaml`. This setting has no effect when you explicitly set a registry, and it is not a setting in the standalone Operator Helm chart. To use a different registry for the Operator pod image, set `image.repository` in your Operator Helm `values.yaml`. |
There was a problem hiding this comment.
For standalone datadog/datadog-operator installs, this now says registryMigrationMode is not an Operator chart setting, but the current standalone Operator chart values list registryMigrationMode (default auto) and use it to add Agent registry override environment variables unless global.registry is set. Users following this section to keep Agent images on the previous site-specific registries with a standalone Operator install would skip the actual registryMigrationMode: "" knob and unexpectedly migrate managed Agent image pulls to registry.datadoghq.com.
Useful? React with 👍 / 👎.
5 participants
What changed
registryMigrationMode.registryMigrationModeis a Datadog Agent Helm chart setting. As of Datadog Operator chart version 2.19.0, when the Operator chart is installed through the Agent chart dependency, it applies to Agent images managed by the Operator; it is not a setting in the standalone Operator Helm chart.image.repositoryvalue.gcr.io/datadoghq/agentor implicit Docker Hub references withregistry.datadoghq.com/agentwhere an explicit Datadog registry image is appropriate.public.ecr.aws/datadog/...where the surrounding docs are AWS/ECS/EKS-specific, and kept Docker Hub as the Operator tag-browsing link.Why
registry.datadoghq.comis the migration target for Agent images, but the resolved Agent image registry can still depend ondatadog.site, cluster type,registryMigrationMode, environment exclusions, and explicit registry overrides. The docs should avoid implying a single universal default or implying thatregistryMigrationModeexists in the standalone Operator Helm chart.Jira
https://datadoghq.atlassian.net/browse/BARX-1838
Validation
git diff --checkrgscan for stale direct Agent/Operator image overrides and oversimplified default-registry wording.