Create architectural blueprint for the CI Cache Service
Overview
Create an architectural blueprint for the CI cache service proposal.
Discuss proposal to create a new CI cache service
User profiles to address
- GitLab.com users with shared runners.
- GitLab.com users with private runners.
- Self-managed instances with private runners.
Concepts and considerations
- Caching service has full control over the caching backend.
- The caching service can be tied to a specific GitLab instance.
- Do not fold the CI cache service into the GitLab monolith that currently handles CI artifacts.
- Start a cache service that's a transparent re-writer.
- Handle authentication to the cache service.
- Conceptually the process will be push a chunk, start another chunk.
- Start with a transparent proxy.
- Customer impact to deploy a new service.
- Handle pre-singed URL's
Edited by Darren Eastman