System administrators may expect the Tanzu Valkey Operator to automatically run administrative and maintenance commands (such as valkey-cli --cluster fix --cluster-fix-with-unreachable-primaries or other cluster repair routines) when a cluster enters a degraded state or experiences lost primary nodes.
However, the operator does not automatically run these structural valkey-cli commands on behalf of the user.
Tanzu for Valkey on Kubernetes
Automated execution of administrative Valkey commands specifically cluster fixes and slot reassignments is deliberately not supported by the Tanzu Valkey Operator.
Preventing Irreversible Data Loss - Commands like --cluster-fix-with-unreachable-primaries force active nodes to claim orphaned hash slots. Executing this automatically during node outages risks permanently overwriting slot mappings and losing all data stored on unavailable nodes.
When administrative actions or slot repairs are required to restore cluster availability, they must be executed manually.