You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So that customers can configure them any of these ways:
252
+
Set redisCache and redisStore endpoints,
253
+
so that customers can configure them any of these ways:
254
+
254
255
1. Create a new Kubernetes secret, with default values (default, no override config required)
256
+
255
257
2. Use an existing Kubernetes secret, by configuring .Values.redisCache.connection.existingSecret
258
+
256
259
3. Do not create or use Kubernetes secrets, just pass the default values directly as environment variables into the needed pods, by configuring .Values.sourcegraph.disableKubernetesSecrets = true
257
-
4. Do not create or use Kubernetes secrets, but pass custom values (ex. external Redis) directly as environment variables into the needed pods, by configuring .Values.sourcegraph.disableKubernetesSecrets = true, .Values.redisCache.connection.endpoint = "", .Values.redisStore.connection.endpoint = "", and defining the REDIS_CACHE_ENDPOINT and REDIS_STORE_ENDPOINT env vars on frontend, gitserver, searcher, and worker pods
260
+
261
+
4. Do not create or use Kubernetes secrets, but provide custom values (ex. external Redis) to have this function pass them into the REDIS_CACHE_ENDPOINT and REDIS_STORE_ENDPOINT env vars on frontend, gitserver, searcher, and worker pods, by configuring:
.Values.redisCache.connection.endpoint = <custom value for REDIS_CACHE_ENDPOINT>,
264
+
.Values.redisStore.connection.endpoint = <custom value for REDIS_STORE_ENDPOINT>,
265
+
266
+
5. Do not create or use Kubernetes secrets, but pass custom values (ex. external Redis) directly as environment variables into the needed pods, by configuring:
0 commit comments