Enable Artifact Registry pull credentials for CI jobs by default

What does this MR do and why?

Sets ci_artifact_registry_pull_credentials to default_enabled: true, so self-managed instances get Artifact Registry pull credentials for CI jobs: a job pulls Artifact Registry images in image: and services: with the job's identity, with no DOCKER_AUTH_CONFIG.

The flag is on globally on GitLab.com (rollout #638660). As agreed with the feature's counterpart, the flag stays in the codebase for one release as a kill switch for self-managed admins, and is removed afterwards.

The flag value is the only change, as the feature flag guidelines ask. The user docs live in the Artifact Registry project (docs/user/formats/docker.md, added in gitlab-org/ops/artifact-registry!3984 (merged)); their version history gets the "enabled by default" line in a separate MR there.

Draft until the flag has been stable on GitLab.com for a few days.

References

Screenshots or screen recordings

n/a, no UI change.

How to set up and validate locally

  1. Without enabling anything, run a job on a Docker-executor runner whose image: is in an Artifact Registry repository of the project's organization, with the job user a member of that organization.
  2. The job payload carries a registry credential for the Artifact Registry host, and the pull succeeds with no DOCKER_AUTH_CONFIG.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

🤖 Generated with Claude Code

Merge request reports

Loading
Loading