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
{{ message }}
Repository navigation
rds-controller: changing optionGroupName on an existing DBInstance has no effect #3181
Describe the bug
Changing spec.optionGroupName on an existing DBInstance is never sent to AWS. The CR reports ACK.ResourceSynced=True, while the instance keeps its old option group.
Same root cause as #3087 (enableIAMDatabaseAuthentication, fixed in rds-controller#327): DescribeDBInstances returns the option group as OptionGroupMemberships[].OptionGroupName, which only goes into status.optionGroupMemberships. Nothing copies it back into the latest spec.
Before v1.7.2 the update sent the full spec, so a change was applied on the next update of any other field.
Steps to reproduce
Create a MySQL DBInstance with optionGroupName: og-a.
Wait until it is available and ACK.ResourceSynced=True.
Create option group og-b (same engine and major version) and set spec.optionGroupName: og-b.
Check aws rds describe-db-instances --query 'DBInstances[0].OptionGroupMemberships' and CloudTrail ModifyDBInstance from the controller.
Expected outcome ModifyDBInstance sends OptionGroupName=og-b, and the instance moves to og-b.
Environment
Kubernetes version: 1.36
Using EKS (yes/no), if so version?: v1.36.5-eks-91f89a9
Hello @Sudokamikaze 👋 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.
Activity
github-actions commentedon Nov 16, 2026
Hello @Sudokamikaze 👋 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.