Integrate Harbor as a proxy cache for GitLab Container Registry
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Organizations using GitLab's Container Registry to host their images for Kubernetes auto-scaling require redundant access to their images. When these images are unavailable, deployments will fail to scale up, and new tasks for orchestration systems will outright fail as well. In practice, this has quickly led to dropped API requests (data loss) and delays in processing data due to tools like Airflow, Spark, Trino, etc not getting the resources they need. All new or scaling workloads would be affected. Integrating Harbor as a local proxy cache provides the required redundancy to prevent outages. This has the added benefits of faster retrieval times for the customer (if the Harbor cache is hosted near the deployment cluster) and reduced egress traffic from the GitLab server.
Problem to solve
- Customers on GitLab.com who use the Container Registry to host images used in their production Kubernetes deployments have experienced outages during GitLab.com service interruptions. This makes the Container Registry unreliable for customers who require redundant access to their container images.
Proposal
- Provide customers the ability to use Harbor as a Proxy Cache to Gitlab Registry.
Intended users
Feature Usage Metrics
Does this feature require an audit event?
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.