Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support update of AuthToken in ElastiCache ReplicationGroup #2255

Open
gfrey opened this issue Jan 31, 2025 · 0 comments
Open

Support update of AuthToken in ElastiCache ReplicationGroup #2255

gfrey opened this issue Jan 31, 2025 · 0 comments
Labels
service/elasticache Indicates issues or PRs that are related to elasticache-controller.

Comments

@gfrey
Copy link

gfrey commented Jan 31, 2025

Describe the bug
When changing the value of the K8s secret field referenced by the AuthToken object in the ReplicationGroup spec, this change should be picked up and applied to ElastiCache.

Steps to reproduce

  1. Create a K8s secret with the original auth-token.
  2. Create a replication group referencing the auth-token from the previous step.
  3. Update the secret from step 1.

In the next reconciliation run, I'd expect the auth-token to be set in the replication group, but there is no such call happening.

Expected outcome
When a change to the value is detected, a ModifyReplicationGroup should be made, containing the new AuthToken value and the AuthTokenUpdateStrategy set to "ROTATE".

Ideally the ACK ReplicationGroup is added a retention period parameter for the old auth-token, that, once gone by, triggers a subsequent ModifyReplicationGroup call, with the AuthTokenUpdateStrategy set to "SET", to remove the old auth-token.

@michaelhtm michaelhtm added the service/elasticache Indicates issues or PRs that are related to elasticache-controller. label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/elasticache Indicates issues or PRs that are related to elasticache-controller.
Projects
None yet
Development

No branches or pull requests

2 participants