Sentinel PVC size inherited from Valkey persistence configuration

Products

• VMware Tanzu Data Suite
• VMware Tanzu for Valkey

Issue/Introduction

When deploying a ValkeySentinel object, the Sentinel pods are assigned Persistent Volume Claims (PVCs) that match the storage size defined in valkeyReplicationConfig.persistence.storageSize. This results in excessive storage allocation for Sentinel pods, which only require minimal space for runtime configuration updates.

Environment

• Product: Tanzu Valkey for Kubernetes
• Component: Valkey-Sentinel
• Version: 3.4.1 and earlier

Cause

The operator currently creates PVCs for Sentinel pods whenever persistence is enabled to store sentinel.conf data. The operator does not currently support independent storage sizing for Sentinel, causing it to inherit the larger Valkey instance size.

Resolution

An enhancement is in release 3.4.2.

In the release 3.4.2, the operator will use an emptyDir mount for writable configuration updates instead of a dedicated PVC. Configuration state will be maintained via ConfigMaps, ensuring settings persist across pod restarts without requiring individual PVCs.