Add the new Redis instance to GitLab-rails and make it configurable in omnibus and the charts
To be able to use the new Redis instance we'll need to add a Gitlab::Redis::RepositoryCache
similar to Gitlab::Redis::Cache
. See gitlab-org/gitlab@33d2c0b6 for an example of how we added Gitlab::Redis::TraceChunks
. In this case the instance will need to fallback to Gitlab::Redis::Cache
.
We'll also need an .active_support_config
to configure an ActiveSupport::Cache::RedisCache
to replace Rails.cache
in Gitlab::RepositoryCache
.
To support configuring this instance in VMs, we'll need to make it configurable in GitLab-omnibus, this is how we've done that for trace chunks gitlab-org/omnibus-gitlab!5316 (merged).
To support configuring the Redis instance in Kubernetes, we'll need to make it configurable in the helm charts. An example of how we did that for trace chunks in gitlab-org/charts/gitlab!2031 (diffs)