Elasticache controller 1.3.0 removing kmsKeyID from ReplicationGroup

[henryzhao95]

Describe the bug
A concise description of what the bug is.

I've recently updated from 0.2.5 of Elasticache ACK to 1.3.0.

I find all my ReplicationGroups are now stuck in a sync loop where kmsKeyID gets removed by the ACK, re-added by Argo CD, removed by the ACK - repeat.

Steps to reproduce
Deploy ReplicationGroup

Expected outcome
In 0.2.5, the kmsKeyID persists in the YAML
Environment

• Kubernetes version
  1.32.9
• Using EKS (yes/no), if so version?
  Yes 1.32
• AWS service targeted (S3, RDS, etc.)
  Elasticache

[github-actions]

Hello @henryzhao95 👋 Thank you for opening an issue in ACK! A maintainer will triage this issue soon.

We encourage community contributions, so if you're interested in tackling this yourself or suggesting a solution, please check out our Contribution and Code of Conduct guidelines.

You can find more information about ACK on our website.