Skip to content

feat(elasticache): support inplace migration to valkey engine#2293

Open
Kunalbehbud wants to merge 1 commit into
crossplane-contrib:masterfrom
Kunalbehbud:feat/elasticache-valkey-migration
Open

feat(elasticache): support inplace migration to valkey engine#2293
Kunalbehbud wants to merge 1 commit into
crossplane-contrib:masterfrom
Kunalbehbud:feat/elasticache-valkey-migration

Conversation

@Kunalbehbud

Copy link
Copy Markdown

Fixes #2290

This PR adds support for in-place ElastiCache ReplicationGroup migration from Redis to Valkey.

It makes spec.forProvider.engine mutable, updates the ElastiCache client logic to pass Engine through ModifyReplicationGroupInput, and extends update detection so engine changes are reconciled correctly. It also updates the AWS SDK dependency to a version that exposes the ElastiCache Valkey support needed by this flow.

Checklist

  • Added unit tests covering engine propagation and update detection
  • Added controller test verifying ModifyReplicationGroupInput includes Engine
  • Regenerated CRDs successfully
  • Ran make test successfully

Signed-off-by: kunal.behbudzade <kunal.behbudzade@btsgrp.com>
@Kunalbehbud

Kunalbehbud commented Apr 15, 2026

Copy link
Copy Markdown
Author

Leaving a ping here in case this fell through the cracks. Happy to adjust the Valkey migration behavior or test coverage if there are concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inplace migrating from ReplicationGroup (ElastiCache) Engine "Redis" to "Valkey" not possible

1 participant