Fix IOPS parameter bug when no volume type is defined

[torredil]

Signed-off-by: Eddie Torres torredil@amazon.com

Is this a bug fix or adding new feature?

• Bug Fix: IOPS parameters is not picked up by driver without defining volume type #1235

What is this PR about? / Why do we need it?

• The IOPS parameter, defined in the StorageClass.parameters, is not picked up by the driver when the volume type is not defined (i.e. defaults to gp3).

Steps to Reproduce

• Create a StorageClass without a volume type but with IOPS

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: test
parameters:
  iops: "6000"
provisioner: ebs.csi.aws.com

• Provision a volume with this StorageClass.

k apply -f claim.yaml

• You'll see that the IOPS values is not honored in the volume created.

 % aws ec2 describe-volumes --volume-id vol-085b747b34dd7f330 --query 'Volumes[0].[Iops, VolumeType]'
[
    3000,
    "gp3"
]

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: torredil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [torredil]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gtxu]

/lgtm