Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #259694
Closed
Open
Issue created Oct 01, 2020 by Michael Kozono@mkozono1️⃣Maintainer

Geo: Replicate Dependency Proxy

From #235434 (comment 405921331):

@mkozono yes I believe it should be replicated. Besides reliability, dependency proxy is about saving on network and time by pulling images from GitLab vs DockerHub. If you can't use it on secondary instance that is geographically close to you then the feature loses some value.

the implementation practically depends on &1528 or some part of it

When we decide to do this, apply the Blob replicator strategy issue template to this description.

Edited Jun 22, 2022 by Michael Kozono
Assignee
Assign to
Time tracking