### Problem to solve It's noted in the [Dependency Proxy documentation](https://docs.gitlab.com/ee/user/packages/dependency_proxy/#limitations) that the feature requires DockerHub being available. This is problematic because when DockerHub is down is when it's more important than ever to be able to pull images from the cache so that you don't experience any downtime. ### Intended users * [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) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### User experience goal - Users have confidence that if they use the Dependency Proxy and DockerHub is down that they won't be impacted by the outage. (assuming their image has been previously cached) ### Proposal Remove the limitation of the Dependency Proxy that DockerHub is available. If DockerHub is down and a requested image exists in the cache, we will pull it from the cache. ### Further details - This is a key requirement for us to dogfood the feature and to reduce our reliance on external dependencies. <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Permissions and Security - There are no permissions changes required for this change. ### Documentation - [Remove limitation](https://docs.gitlab.com/ee/user/packages/dependency_proxy/#limitations) ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? - Success looks like users are able to use the proxy to improve their reliability and efficiency. - Measure the cache hit ratio. (issue to add instrumentation to the dependency proxy https://gitlab.com/gitlab-org/gitlab/-/issues/238056) ### What is the type of buyer? - This will be a Premium feature <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references <!-- Label reminders - you should have one of each of the following labels if you can figure out the correct ones -->