allowAutoIOPSPerGBIncrease should be honored on volume resize

[heybronson]

Is your feature request related to a problem? Please describe.
When allowAutoIOPSPerGBIncrease is enabled for a storage class, it's only honored on the initial CreateDisk call: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/pkg/cloud/cloud.go#L581

Subsequent volume resizes do not consider allowAutoIOPSPerGBIncrease, meaning IOPS is never recalculated with the new disk size.

Describe the solution you'd like in detail
allowAutoIOPSPerGBIncrease should be honored and IOPS should be recalculated when a persistent volume is resized.

[torredil]

Hi @heybronson, the allowAutoIOPSPerGBIncrease parameter is relevant on the provisioning path when iopsPerGB is specified by essentially raising the IOPS to the minimum valid value. In other words, resizes after the volume is provisioned are guaranteed to be at or above that minimum valid value.

It sounds like #1698 would address the request here - can you confirm?

[torredil]

/kind feature

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mdzraf]

/remove-lifecycle stale