Feature Overview (aka. Goal Summary)  

Support configuring the storage of Repo Server, so that customer can handle large git repositories

Goals (aka. expected user outcomes)

The goal of this feature is to provide customers an option to allocate a larger storage space for handling large Git repositories to be cached in the repository server.

Requirements (aka. Acceptance Criteria):

• Default storage should be kept as EmptyDir
• User should be able to override the storage specification in the ArgoCD CR under the `spec.repositoryServer` section.
• Customers should be able to specify capacity, retention policy and storage class

Questions to Answer:

Out of Scope

• Storage specification for other ArgoCD components are not covered here.

Background

Currently ArgoCD Repo server uses EmptyDir as the storage volume type with no fixed capacity specified. This will use Nodes ephemeral storage and is limited. For Customers who have larger manifests and operating with too many repositories, this storage space may not be sufficient. By providing an option to customers for providing a larger storage capacity, customers can work with larger repos and manifests.

Documentation Considerations

• Newly added spec fields should be documented in the user guide.
• This new feature should be captured in the release notes.