docs: add explicit warning for redis single replica configuration #382
+8
−0
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.
Summary
This PR adds an explicit warning in the
values.yamldocumentation about the requiredmin-replicas-to-write: 0configuration when using Redis HA with a single replica.Problem
When users configure
redis-ha.replicas: 1, Redis by default requires at least one secondary replica to accept writes. Without settingmin-replicas-to-write: 0, users encounter the error:Solution
This PR adds an IMPORTANT note directly after the
replicas: 1setting, making it immediately clear that users must also configuremin-replicas-to-write: 0when using a single replica setup.Changes:
replicas: 1for visibilityWhy supersede #359?
While #359 identified the same issue, this PR improves the documentation by:
replicas: 1instead of afterpersistentVolumeValidation
This configuration is already used in the project's CI tests:
helm/oauth2-proxy/ci/redis-standalone-values.yaml:29Supersedes #359
Ref: https://stackoverflow.com/a/59737862