You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix Redis to Valkey in-place upgrade by handling Engine in ModifyReplicationGroup (#188)
Fixes: aws-controllers-k8s/community#2299
Description of changes:
fixes the issue where in-place upgrades from ElastiCache Redis to Valkey clusters failed with `InvalidParameterCombination: valkey parameter group is not applicable to engine redis`. The problem occurred because the ElastiCache controller's custom `ModifyReplicationGroup` implementation was missing the `Engine` and `CacheParameterGroupName` fields in the API request payload, causing AWS to reject Valkey parameter groups being applied to what it perceived as a Redis engine. Additionally, the `ModifyReplicationGroup` API returns stale field values that don't immediately reflect requested changes, leading the controller to detect false differences and trigger terminal conditions. The solution adds both missing fields to the modify request payload, and normalizes API responses by overriding stale Engine field values with the user's intended values before processing.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
0 commit comments