-
Notifications
You must be signed in to change notification settings - Fork 16
feat: Add Valkey cache for scaling #700
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
base: main
Are you sure you want to change the base?
Conversation
|
Need to decide if we are happy with no auth to start with here? |
If we are not going to store fragile data in the cache, I'm ok with no auth + network policy that will allow connections to the cache from the Forge deployment only. |
Co-authored-by: PPawlowski <ppawlowski@users.noreply.github.com>
6717f22 to
4326bd0
Compare
|
@ppawlowski i rebased this on main to resolve some merge conflicts, can you double check the |
|
@ppawlowski I'm going to merge this, we should be aware this will deploy Valkey (even with a single Forge app instance) when the CloudProject helm version releases are updated. |
Go for it. |
fixes #699
Description
Adds a Valkey instance if more than 2 Forge app instances are configured.
Related Issue(s)
#699
FlowFuse/flowfuse#3642
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel