Automated Execution of Valkey Commands by the Operator Is not Supported in Tanzu for Valkey on Kubernetes
search cancel

Automated Execution of Valkey Commands by the Operator Is not Supported in Tanzu for Valkey on Kubernetes

book

Article ID: 450556

calendar_today

Updated On:

Products

VMware Tanzu Data Intelligence

Issue/Introduction

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.


Environment

Tanzu for Valkey on Kubernetes

Cause

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.

Resolution

When administrative actions or slot repairs are required to restore cluster availability, they must be executed manually.