docs: recommend redis when users want to use a cache for renovate

The disk cache is very likely to pile up quickly. This will prevent the Job to be executed once the PersistentVolume is full. More information can be found here: renovatebot/renovate#30525 Signed-off-by: Tim Beermann <[email protected]>
renovatebot · Dec 10, 2024 · a496f3c · a496f3c
1 parent 716da0f
commit a496f3c
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 0 deletions.
diff --git a/charts/renovate/README.md.gotmpl b/charts/renovate/README.md.gotmpl
@@ -44,6 +44,8 @@ To speed up execution time of jobs it could be useful to enable persistent cachi
 can make use of the cache that have been build up in previous runs. Set `renovate.persistence.cache.enabled` to true
 to enable this. If necessary, the storageClass can be configured and the storageSize can be set to the preferred value.
 
+**HINT**: It is highly recommended to use the redis subchart or SQLite for caching, instead of disk caching.
+Take a look at https://github.com/renovatebot/renovate/discussions/30525 for more information.
 
 ## Renovate config templating
 

diff --git a/charts/renovate/values.yaml b/charts/renovate/values.yaml
@@ -108,6 +108,9 @@ renovate:
   # -- Renovate Container-level security-context
   securityContext: {}
 
+  # Instead of a file system cache, it is highly recommended to use the redis subchart.
+  # Alternatively, SQLite is also a good choice.
+  # Take a look at https://github.com/renovatebot/renovate/discussions/30525 for more information.
   # -- Options related to persistence
   persistence:
     cache: