Robin cannot authenticate to Valkey nodes when auth.secret is configured

[Lyonk71]

Description

When auth.secret is configured on a RedkeyCluster CR, the operator correctly sets requirepass on the Valkey pods via the StatefulSet config. However, Robin is never given the password — it has no auth handling in its codebase (internal/robin/robin.go has zero references to auth/password/secret).

This causes Robin to fail with failed to connect after 10 retries on every node, leaving the cluster permanently stuck in Configuring status.

Steps to Reproduce

1. Create a Secret with a requirepass key
2. Configure a RedkeyCluster CR with auth.secret pointing to that secret
3. Observe Robin logs: Error initializing node ... "failed to connect after 10 retries"

Expected Behavior

Robin should receive the auth credentials (via configmap or environment variable) and use them when connecting to Valkey nodes.

Workaround

Remove auth.secret from the CR and use a NetworkPolicy to restrict access instead.

Environment

• Redkey Operator v0.1.0
• Robin v0.1.0
• OpenShift 4.18 / OKD
• Valkey 8

[DanielDorado]

Hi @Lyonk71,

In our current, closed-source system, all the logic that Robin does, except for the metrics, was done by the operator.

We re-architect it to delegate cluster management to Robin to reduce the burden on the operator, so that one operator can manage the largest number of Redis clusters. As our tests are done without authentication, and we are still not using it in production, we miss it.

To summarize, you are right, and we will fix it as soon as possible. However, we are currently pausing our Redis migration to this open-source operator while we migrate other systems. PRs are welcome.

Thanks,