Set Object Storage Direct Upload to On as default
Problem to solve
We are starting to shift more and more of our customers to an NFS-free architecture. Our current dependencies on NFS are Pages and Gitaly (until HA) but once these no longer require NFS, we will rapidly move away from recommending it anywhere. In fact for many deployments, we are already no longer recommending NFS.
With the move away from NFS, background upload to object storage will no longer work, as it depends upon shared storage. Without NFS, the current default (direct uploads disabled) won't work.
Note that live job tracing does use direct uploads, provided direct uploads flag is enabled.
Intended users
Further details
Context from Product scaling agenda: https://docs.google.com/document/d/1nMJzrDfG7C14WP5v7P226oPFuXkwqIk7bdIT8ai0DNU/edit?ts=5d84fb07&skip_itp2_check=true&pli=1#bookmark=id.bsy4i16awahh
Proposal
Enable Direct Upload and consider making this the default behavior to reduce the possibilities of configuration error with the more recent architectures.
Technical Proposal
- Remove the user-facing setting for
direct_upload
andbackground_upload
because they are exclusive and users cannot activate both upload strategies simultaneously. - Automatically set
direct_upload/background_upload
based on whether object storage is configured
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
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.