Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions charts/renovate/README.md.gotmpl
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
3 changes: 3 additions & 0 deletions charts/renovate/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -116,6 +116,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:
Expand Down