GitLab Chart issueshttps://gitlab.com/gitlab-org/charts/gitlab/-/issues2021-12-31T09:52:26Zhttps://gitlab.com/gitlab-org/charts/gitlab/-/issues/794Implement extraKey for all object storage secrets2021-12-31T09:52:26ZJason PlumImplement extraKey for all object storage secrets## Summary
From [this comment on #712](https://gitlab.com/charts/gitlab/issues/712#note_97902903), some users will not be allowed to make use of GCS's XML compatible API (access/secret keys). We should investigate the feasibility and ti...## Summary
From [this comment on #712](https://gitlab.com/charts/gitlab/issues/712#note_97902903), some users will not be allowed to make use of GCS's XML compatible API (access/secret keys). We should investigate the feasibility and time needed to implement the `extraKey` implementation to all object storage secrets & charts that use them.
## Detail
Fog accepts `google_json_key_string` or `google_json_key_location`. Currently, the only way to use the GCS JSON API is to provide each secret with the contents of `google_json_key_string`. We have a working example (`registry`) of how to implement and work with the `extraKey`, which would allow implementation of `google_json_key_location` usage.
~~We also need to investigate the abilities of the task-runner / backups with s3cmd.~~ task-runner has support for GCS.Backloghttps://gitlab.com/gitlab-org/charts/gitlab/-/issues/398Make a global storageClass setting that can easily be applied to all our charts2020-08-14T15:53:14ZDJ Mountneydj@gitlab.comMake a global storageClass setting that can easily be applied to all our chartsThis will make it easier to use a custom storageClass for all the PVCs. And based on my testing, most production installs of GitLab are going to want to use a custom storageClass that has a reclaimPolicy of `Retain`.This will make it easier to use a custom storageClass for all the PVCs. And based on my testing, most production installs of GitLab are going to want to use a custom storageClass that has a reclaimPolicy of `Retain`.Backlog