rds DBInstance gp3 iops/storageThroughput reconciliation loop

[saatvik-chugh]

What happened?

For RDS DBInstances using gp3 storage, provider-aws can enter a reconciliation loop around iops and/or storageThroughput when AWS returns or normalizes values differently from the spec.

There is an existing open issue #2302 and PR #2301, but opening this as a fresh user-facing report because this is still affecting current usage and may need maintainer attention.

How can we reproduce it?

Create or manage an RDS DBInstance using gp3 storage where iops or storageThroughput are set or late-initialized. Observe that provider-aws continues to detect drift and attempt updates.

Conceptual example:

apiVersion: rds.aws.crossplane.io/v1alpha1
kind: DBInstance
spec:
  forProvider:
    region: us-east-1
    storageType: gp3
    allocatedStorage: 100
    iops: 3000
    storageThroughput: 125

What environment did it happen in?

Provider version: v0.56.0 / v0.58.0
Crossplane version:
Kubernetes version:
AWS region:
Engine:
Instance class:

Expected behavior

Provider-aws should not continuously attempt updates when the RDS gp3 configuration is already valid or when AWS normalizes default gp3 values.