When using the Valkey Operator, users may observe that updating resource requests and limits in the ValkeySentinel object after initial deployment does not reflect in the running pods or underlying StatefulSets.
For example:
ValkeySentinel resource is created successfullyValkeySentinel YAMLThis may give the impression that the operator is not reconciling or applying resource updates.
This behavior is due to how the Valkey Operator manages resources:
ValkeySentinel and ValkeyReplication are separate resources with distinct responsibilities.ValkeySentinel can create a ValkeyReplication resource during initial deployment, subsequent updates to resources must be applied to the correct component.ValkeySentinelValkeyReplicationUpdating only the ValkeySentinel object does not automatically propagate changes to the ValkeyReplication resource after it has been created.
To update resources for:
Sentinel pods: Update resource requests and limits in the ValkeySentinel object.
Valkey (data) pods: Update resource requests and limits in the ValkeyReplication resource.