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
I will get the secret specified. Additionally, when I delete that claim, the secret will also be deleted.
What I am finding however is that while the secret is created and populated as expected when the claim is made it is not removed when the claim is deleted even though the RDS DBInstance is deleted.
The secret handling for RDS resources has been rewritten in #1756. Now the generated passwords will be stored in a separate cache secret that is removed upon MR deletion. However, a secret referenced through spec.forProvider.masterUserPasswordSecretRef will not be deleted by the controller.
Closing this now, as this issue is probably not relevant anymore with the current implementation. Feel free to reopen if that is not the case.
What happened?
I expect that when creating DBInstance using rds.aws.crossplane.io/v1alpha1 and specifying masterUserPasswordSecretRef with the following
I will get the secret specified. Additionally, when I delete that claim, the secret will also be deleted.
What I am finding however is that while the secret is created and populated as expected when the claim is made it is not removed when the claim is deleted even though the RDS DBInstance is deleted.
How can we reproduce it?
What environment did it happen in?
Crossplane version: crossplane:v1.10.2-up.1
Provider: xpkg.upbound.io/crossplane-contrib/provider-aws:v0.37.0
I am running a v1.24.8-eks-ffeb93d cluster on AWS.
The text was updated successfully, but these errors were encountered: