Yasar Rahman 8be7fb2e66 feat(redis): expose min-replicas-to-write and min-replicas-max-lag ...

Lets an operator bound the writes lost when an isolated Redis master is
failed over: the master refuses writes while fewer replicas than
configured are connected and recent. Both values are unset by default, so
the rendered Redis config is unchanged.

Redis treats 0 in either directive as disabling the check, so the
chart refuses minReplicasMaxLag 0 next to a replica requirement
instead of silently turning the protection off.

Negative values are refused by the schema (minimum 0), since Redis
rejects them at CONFIG SET and the operator would stop healing the
Sentinels of that instance. A requirement of replicas or more is
refused at render: a master with replicas pods has replicas-1
replicas, so it would refuse every write for good.

Assisted-by: LLM
Signed-off-by: Yasar Rahman <yasar.rehman@gmail.com>

2026-10-12 02:03:17 +05:00

..

min_replicas_test.yaml

feat(redis): expose min-replicas-to-write and min-replicas-max-lag

2026-10-12 02:03:17 +05:00

sentinel_image_test.yaml

feat(redis): run Sentinel on the same image as the Redis pods

2026-10-11 13:16:11 +05:00

sentinel_resources_test.yaml

feat(redis): size the Sentinel pods separately from Redis

2026-10-11 00:27:32 +05:00

tenant_projection_test.yaml

feat(redis): declare the tenant trust anchor as a TenantProjection

2026-09-02 17:58:05 +03:00

tls_test.yaml

feat(redis,postgres): certify the per-engine external hostname

2026-10-07 04:43:15 +03:00