Enable Docker dependency proxy for projects in personal namespace

Release notes

Enable Docker dependency proxy for projects in personal namespace

Problem to solve

As a personal user with public open-source projects in my personal namespace, I want to use the Docker dependency proxy, so that I can save execution time in pipelines and avoid hitting the Docker Hub rate limit.

Intended users

• Sasha (Software Developer)
• Devon (DevOps Engineer)

In this use case, I am both Sasha and Devon at the same time.

User experience goal

There should be a CI/CD variable available to prefix the image:name: field in a .gitlab-ci.yml file in order to use the Docker dependency proxy, just like for group namespaces.

Proposal

Solve it the same way as for groups, only for personal namespaces instead.

Further details

N/A.

Permissions and Security

• Add expected impact to Developer (30) members
• Add expected impact to Maintainer (40) members
• Add expected impact to Owner (50) members

The above is only relevant for projects with shared access.

Documentation

Should probably be added to the [Dependency proxy](https://docs.gitlab.com/ee/user/packages/dependency_proxy/] docs.

Availability & Testing

No idea.

Available Tier

Free, for public personal open-source projects at least.

What does success look like, and how can we measure that?

Public personal open-source projects are able to use the Docker dependency proxy just like if the project was in a group namespace.

What is the type of buyer?

Single-person open-source project maintainers.

Is this a cross-stage feature?

No idea.

Links / references

N/A.