Registry Persistence
Spawned from https://gitlab.com/charts/helm.gitlab.io/issues/99
Currently, the Registry chart supports persistence via the configuration of the storage values in the chart. This means that the user could configure any particular storage they want, from an external service. We currently recommend s3
or gcs
for this, but some user may wish to use filesystem
which would require persistent (likely multi-access) storage.
I believe the storage for the Registry chart certainly falls to leaning towards in-cluster object storage such as Minio, but we also need to evaluate the IOPs needs for disks, and possible methods for using filesystem
driver with replicas
> 1
We should map & document the methods we see as the best approaches for multiple kinds of deployments. Hosted services (GKE/AKS), local (minikube), self-hosted (kops/kubespray/Tectonic/Rancher).