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
Copy file name to clipboardExpand all lines: docs/guides/configure_memcached.markdown
+26-2Lines changed: 26 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,11 @@ has_toc: false
17
17
---
18
18
# Configuring memcached as the caching store
19
19
20
-
If you want to use [memcached](https://memcached.org/) as a caching store, you first have to deploy it separately (e.g. via separate helm chart). The existing deployments can be referenced in the `values.yaml` so that they are used as caching stores.
20
+
If you want to use [memcached](https://memcached.org/) as a caching store, you first have to deploy it separately (e.g. via a dedicated helm chart). The existing deployments can be referenced by two approaches.
21
21
22
-
Here's how to configure the memcached's via the values:
22
+
## Referencing memcached stores via values
23
+
24
+
Here's how to configure preexisting memcached deployment with their dedicated `memcached-*` sections in the chart values:
23
25
24
26
{% raw %}
25
27
```yaml
@@ -41,3 +43,25 @@ memcached-blocks-metadata:
41
43
containerPort: 11211
42
44
```
43
45
{% endraw %}
46
+
47
+
## Referencing via `extraArgs`
48
+
49
+
You can also omit the `memcached-*` sections entirely and use the `extraArgs` of each cortex component to reference an existing memcached deployment.
0 commit comments