feat: switch valkey dependency to official valkey-io chart#939
Merged
Conversation
Contributor
|
I'll try and test this today |
hardillb
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This pull request replaces the
valkeychart dependency from CloudPirates (oci://registry-1.docker.io/cloudpirates, version 0.15.3) with the officialvalkey-io/valkey-helmchart (https://valkey.io/valkey-helm/, version 0.9.4).Motivation: CloudPirates have announced the deprecation of their Valkey chart in CloudPirates-io/helm-charts#1083 and recommend the upstream chart as the replacement.
NOTE: the information below about chart behaviour with default and custom values will be added to the README file after the release.
Behaviour for default values
forge.localValkey: truewith thevalkey:block at defaults: transparent upgrade.StatefulSet→Deployment(the official chart uses a Deployment for standalone mode).<release>-valkey:6379).Behaviour for custom
valkey:overridesUpstream uses a different values schema. Users who override keys under
valkey:need to translate them:valkey.persistence.enabledvalkey.dataStorage.enabledvalkey.persistence.sizevalkey.dataStorage.requestedSizevalkey.persistence.storageClassvalkey.dataStorage.classNamevalkey.config.maxMemoryvalkey.valkeyConfigraw stringvalkey.config.maxMemoryPolicyvalkey.valkeyConfigraw stringvalkey.config.savevalkey.valkeyConfigraw stringvalkey.replicaCountvalkey.replica.replicas(withvalkey.replica.enabled: true)valkey.architecturevalkey.replica.enabled(sentinel mode is no longer supported)valkey.auth.passwordvalkey.auth.aclUsers.default.password(ACL model)Related Issue(s)
Closes #882
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel