Yasar Rahman 9a88afe6ca feat(redis): run Sentinel on the same image as the Redis pods ...

The Sentinels were left on redis:6.2.6-alpine when the operator moved to
the freshworks-oss fork, so that its new compiled-in default could not
move them on upgrade. 6.2 is end of life, and every instance now runs a
Sentinel one or two major versions behind the Redis it monitors.

The rollback risk behind that pin, a newer engine rewriting dump.rdb in
a format the older one cannot load, does not apply to Sentinel. It
stores no RDB or AOF, only sentinel.conf on an emptyDir that the
config-copy init container rewrites from the operator's ConfigMap on
every start, so moving back to an older image starts from a clean
config. Taking the image from the same version map as the data pods also
means one image per node instead of two.

The e2e comment that relied on busybox's timeout exit code in the
Sentinel container is updated, since that container now carries
coreutils.

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

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

..

chainsaw-test.yaml

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

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

redis-flip-tls.yaml

test(redis): exercise TLS end to end in the chainsaw suite

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

redis-flip.yaml

test(redis): exercise TLS end to end in the chainsaw suite

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

redis-tls.yaml

test(redis): exercise TLS end to end in the chainsaw suite

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

redis.yaml

test(e2e): migrate app suite from BATS to Chainsaw and wire into CI

2026-06-25 13:42:34 +05:00