Feat/support valkey sentinel#238
Open
Renaud Hager (renaudhager) wants to merge 5 commits intomainfrom
Open
Conversation
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
1 participant
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.
This pull request adds support for configuring Redis Sentinel for both session and worker cache backends in the Shopware Helm chart. It introduces new configuration blocks for Sentinel, updates the template logic to use them when enabled, and ensures backward compatibility with existing Redis and Valkey setups.
Requires Shopware Operator version >=
0.0.74.Redis Sentinel support:
valkeysessionSentinelandvalkeyworkerSentinelinvalues.yamlto allow enabling and specifying host, port, and dbindex for Redis Sentinel connections.Template logic updates:
store.yamlto use Redis Sentinel DSN for session cache whenvalkeysessionSentinel.enabledis true, falling back to existing Redis/Valkey logic otherwise.store.yamlto use Redis Sentinel DSN for worker cache whenvalkeyworkerSentinel.enabledis true, falling back to existing Redis/Valkey logic otherwise.