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
When creating RDSInstance with storageType equal gp3 and allocatedStorage set to 200gib (under 400gib). IOPS is then automatically set to correct baseline of 3000. When then editing the RDSInstance by increasing the allocatedStorage to 2000gib (over 400 gib), the IOPS should be automatically increased to 12 000. AWS will automatically increase the IOPS to the new baseline (can confirm in the AWS console), but crossplane-provider will try to reconcile it back to the previous value of 3000. 3000 IOPS is not valid for allocatedStorage over 400gib, the new treshold is now 12 000 and no longer 3000. A reconcile error happens. I expected the crossplane provider to not try to renconcile it back to 3000 but to be updated with the updated IOPS value from AWS: 12 000 which was set by AWS automatically when updating the allocatedStorage parameter, the storage of the RDSInstance.
How can we reproduce it?
First create a RDSInstance with allocatedStorage set to 200gib (<400) and storageType equal to gp3.
Confirm in the AWS console the IOPS is set to 3000.
Then edit the RDSInstance by increasing the allocatedStorage to 600 (>400) gib.
Confirm in the AWS console the IOPS is set to 12 000.
Describe the RDSInstance and verify the reconcile error with message something like this: Invalid iops value for engine name postgres and storage type gp3: 3000","requestParameters":{"allowMajorVersionUpgrade":true,"dBInstanceIdentifier":"instance-x-db","iops":3000,"multiAZ":true,"applyImmediately":true}
What happened?
When creating
RDSInstance
withstorageType
equalgp3
andallocatedStorage
set to 200gib (under 400gib).IOPS
is then automatically set to correct baseline of 3000. When then editing theRDSInstance
by increasing theallocatedStorage
to 2000gib (over 400 gib), theIOPS
should be automatically increased to 12 000. AWS will automatically increase theIOPS
to the new baseline (can confirm in the AWS console), but crossplane-provider will try to reconcile it back to the previous value of 3000. 3000IOPS
is not valid forallocatedStorage
over 400gib, the new treshold is now 12 000 and no longer 3000. A reconcile error happens. I expected the crossplane provider to not try to renconcile it back to 3000 but to be updated with the updated IOPS value from AWS: 12 000 which was set by AWS automatically when updating theallocatedStorage
parameter, the storage of theRDSInstance
.How can we reproduce it?
First create a RDSInstance with allocatedStorage set to 200gib (<400) and storageType equal to gp3.
Confirm in the AWS console the IOPS is set to 3000.
Then edit the RDSInstance by increasing the allocatedStorage to 600 (>400) gib.
Confirm in the AWS console the IOPS is set to 12 000.
Describe the RDSInstance and verify the reconcile error with message something like this:
Invalid iops value for engine name postgres and storage type gp3: 3000","requestParameters":{"allowMajorVersionUpgrade":true,"dBInstanceIdentifier":"instance-x-db","iops":3000,"multiAZ":true,"applyImmediately":true}
Environment
Crossplane version: v1.15.0
kubectl version: v1.29.1
crossplane/provider-aws@v0.32.0
Resource: apiVersion: database.aws.crossplane.io/v1beta1, kind: RDSInstance
Linux Redhat 8.9
-->
The text was updated successfully, but these errors were encountered: