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
Both the instance and the subnetgroup are created succesfully, but the instance constantly goes in and out of a "modifying" state.
The following event appears on the instance resource:
Normal UpdatedExternalResource 4m41s (x78 over 40m) managed/rdsinstance.database.aws.crossplane.io Successfully requested update of external resource
A bit of digging, and it seems that the ParameterGroup is being "updated" on the instance every few minutes, and so the instance itself keeps flipping-in-and-out-of a Modifying state.
I don't understand why this is occurring and I'm so far unable to troubleshoot further, there's nothing logged by the provider to suggest why it's making this change. I appreciate that I should perhaps be opening this issue against the provider and not crossplane, but some general guidance about how to troubleshoot this would be appreciated, thanks.
What happened?
I'm observing the following issue when managing an RDSInstance with crossplane.
The resource manifest for the RDSInstance is as follows:
Both the instance and the subnetgroup are created succesfully, but the instance constantly goes in and out of a "modifying" state.
The following event appears on the instance resource:
A bit of digging, and it seems that the ParameterGroup is being "updated" on the instance every few minutes, and so the instance itself keeps flipping-in-and-out-of a
Modifying
state.I don't understand why this is occurring and I'm so far unable to troubleshoot further, there's nothing logged by the provider to suggest why it's making this change. I appreciate that I should perhaps be opening this issue against the provider and not crossplane, but some general guidance about how to troubleshoot this would be appreciated, thanks.
What environment did it happen in?
Crossplane version: 1.0
Kubernetes version: (EKS) 1.18, kubectl 1.18
The text was updated successfully, but these errors were encountered: