MAS CLI detects `efs` storage when it's not in cluster in AWS

[mudspringhiker]

MAS CLI version

13.3.1

CLI function used

install

What happened?

When installing MAS on cluster (SNO in this case) provisioned on AWS (using mas provision-aws), the installer detects efs as one of the storage classes when it's not configured in the cluster.

Relevant log output

5) Configure Storage Class Usage
Maximo Application Suite and it's dependencies require storage classes that support ReadWriteOnce (RWO) and ReadWriteMany (RWX) access modes:
  - ReadWriteOnce volumes can be mounted as read-write by multiple pods on a single node.
  - ReadWriteMany volumes can be mounted as read-write by multiple pods across many nodes.

Storage provider auto-detected: AWS GP3
  - Storage class (ReadWriteOnce): gp3-csi
  - Storage class (ReadWriteMany): efs
Use the auto-detected storage classes? [y/n] n
Select the ReadWriteOnce and ReadWriteMany storage classes to use from the list below:
Enter 'none' for the ReadWriteMany storage class if you do not have a suitable class available in the cluster, however this will limit what can be installed
  - gp2-csi
  - gp3-csi
ReadWriteOnce (RWO) storage class gp3-csi
ReadWriteMany (RWX) storage class gp3-csi

---

[ibmmas/cli:13.13.1]mascli$ oc get sc
NAME                PROVISIONER       RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
gp2-csi             ebs.csi.aws.com   Delete          WaitForFirstConsumer   true                   32m
gp3-csi (default)   ebs.csi.aws.com   Delete          WaitForFirstConsumer   true                   32m