Andrey KolkovandClaude Opus 4.8 ec0785fe2a fix(redis-operator): use REDISCLI_AUTH for valkey-cli auth in generated scripts ...

The freshworks-oss operator authenticates the CLI in its generated
readiness and shutdown scripts by exporting the engine's auth env var
before invoking it. For the Valkey engine it used VALKEYCLI_AUTH, but
valkey-cli honours only REDISCLI_AUTH (its --help documents that name and
no VALKEYCLI_AUTH). With auth enabled the readiness probe's valkey-cli
call therefore returned NOAUTH, the role never resolved, and the data
pods never became Ready.

Patch valkeyEngine.CLIAuthEnvName to REDISCLI_AUTH so auth-enabled Valkey
instances pass readiness.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Andrey Kolkov <androndo@gmail.com>

2026-09-01 14:41:32 +04:00

..

charts/redis-operator

feat(redis-operator): migrate from archived spotahome to freshworks-oss fork

2026-08-19 10:15:57 +02:00

images/redis-operator

fix(redis-operator): use REDISCLI_AUTH for valkey-cli auth in generated scripts

2026-09-01 14:41:32 +04:00

Chart.yaml

Calculate tags and version automatically (#100)

2024-04-24 11:31:22 +02:00

Makefile

feat(redis-operator): migrate from archived spotahome to freshworks-oss fork

2026-08-19 10:15:57 +02:00

values.yaml

fix(redis-operator): set required OPERATOR_GROUP_ID for the freshworks fork

2026-08-19 10:15:58 +02:00