Update Redis cache server edgi-govdata-archiving/web-monitoring#119

Our previous cache was in us-east-1, which is very far away from where our services are now (they used to be on Heroku, which was in us-east-1). I've set up a new Redis instance in us-west-2 and incremented the `api` and `import-worker` configs here so they pick up the new value (it's in the secrets file, which you can find in Keybase).
edgi-govdata-archiving · Nov 19, 2018 · 77a5dc3 · 77a5dc3
1 parent bb23993
commit 77a5dc3
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/templates/production/api-deployment.yaml b/templates/production/api-deployment.yaml
@@ -97,6 +97,11 @@ spec:
           value: enabled
         - name: REDIS_URL
           value: redis://redis-master:6379
+        - name: REDIS_CACHE_URL
+          valueFrom:
+            secretKeyRef:
+              name: app-secrets
+              key: redis_cache_url
         - name: SECRET_KEY_BASE
           valueFrom:
             secretKeyRef:

diff --git a/templates/production/import-worker-deployment.yaml b/templates/production/import-worker-deployment.yaml
@@ -109,4 +109,4 @@ spec:
               name: app-secrets
               key: token_private_key
         - name: INCREMENTAL_UPDATE
-          value: "3"
+          value: "4"