Valkey Operator Does not update Resource Requests and Limits when modified in ValkeySentinel
search cancel

Valkey Operator Does not update Resource Requests and Limits when modified in ValkeySentinel

book

Article ID: 437190

calendar_today

Updated On:

Products

VMware Tanzu Data Intelligence VMware Tanzu Gemfire VMware Tanzu Greenplum VMware Tanzu Data Suite VMware Tanzu Data VMware Tanzu RabbitMQ RabbitMQ VMware Tanzu for MySQL VMware Tanzu for Postgres VMware Tanzu for Valkey

Issue/Introduction

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:

  • A ValkeySentinel resource is created successfully
  • Resource requests/limits are later modified in the ValkeySentinel YAML
  • However, no changes are observed in:
    • Existing pods
    • StatefulSets
    • Or Valkey instances

This may give the impression that the operator is not reconciling or applying resource updates.

Cause

This behavior is due to how the Valkey Operator manages resources:

  • ValkeySentinel and ValkeyReplication are separate resources with distinct responsibilities.
  • While ValkeySentinel can create a ValkeyReplication resource during initial deployment, subsequent updates to resources must be applied to the correct component.
  • Resource configurations for:
    • Sentinel pods is managed via ValkeySentinel
    • Valkey (data) pods is managed via ValkeyReplication

Updating only the ValkeySentinel object does not automatically propagate changes to the ValkeyReplication resource after it has been created.

Resolution

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.