Repository navigation
Stop forcing appendonly yes on persistent clusters - #78
Merged
Merged
Conversation
Signed-off-by: Alberto Martínez Pérez <albertompe@ext.inditex.com>
…hange Signed-off-by: Alberto Martínez Pérez <albertompe@ext.inditex.com>
pablool05
approved these changes
Oct 26, 2026
pablool05
approved these changes
Oct 26, 2026
DanielDorado
approved these changes
Oct 26, 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.
Summary
Closes #77.
Robin no longer forces
appendonly yeson persistent (ephemeral: false) clusters. Each persistence directive is now written by exactly one layer:appendonly/savewritten byephemeral: trueappendonly no+save ""), unchangedephemeral: falsespec.configsave 3600 1 300 100 60 10000The AOF/RDB decision for persistent clusters goes back to the user. The generated
redis.confalso stops repeating directives that clients such as the Helm chart already set explicitly.Changes
internal/kubernetes/objects.go:buildRedisConfdrops theelse { appendonly yes }branch and documents the ownership.internal/kubernetes/objects_test.go:TestBuildRedisConf_PersistenceOwnershipover{ephemeral, persistent} × {cluster, standalone} × {no user persistence, user enables, user disables}. It counts directive lines:appendonly no/save ""appear exactly once, before the user config;TestBuildConfigMap_Ephemeral/TestBuildConfigMap_NonEphemeralupdated.CHANGELOG.md: breaking-change entry with migration notes.Breaking change
Persistent clusters that do not set
appendonlyinspec.configwill no longer have AOF enabled. They fall back to the Redis defaults: RDB snapshots with the default save points, AOF off.dump.rdbwritten at shutdown. Ifspec.configsetssave "", it starts empty.appendonly yes(andsave ...if needed) tospec.configof persistent clusters to keep AOF.save/appendonly.Additional context
go test ./internal/...: 617 passed.make test-integration: 58/58.make lint: 0 issues.persistencepassed 5/5 on kind with this Robin build.saveline RDB stays on with the default save points; without anappendonlyline AOF stays off.