Move the Dependency Proxy to Core
<!-- This issue template can be used a great starting point for feature requests. The last section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve When determining if a feature should be Paid-only or included in Core, we ask ourselves who benefits from this feature. When considering the Dependency Proxy, it's clear that proxying and caching images from Docker Hub is common practice for all types of organizations and buyers. In fact, as we consider expanding this feature to allowing proxying and caching of packages from external repositories, such as npmjs.com or maven-central, this functionality should also be included in Core as these are common workflows for all individual contributors. ### Proposal Ensure that proxying and caching images or packages from the most common public, remote repositories are included in Core, so that Developers can improve the reliability and performance of their builds. #### Supported repositories - Docker Hub - npmjs.com (proxying only) #### In the future we'll also support - NuGet.org - mvnrepository.com - pypi.org - conan-central ### Intended users Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone- ### User experience goal - All GitLab users can reliably proxy and cache images from Docker Hub using the Dependency Proxy
issue