1. Proposed title of this feature request
Install a storage operator and create a default storage class.

2. What is the nature and description of the request?
After installing OpenShift, the OpenShift console presents a few action items for the user to complete, such as setting up an authentication provider and configuring alerts. It should also present installing a storage operator and creating a default storage class as an important action item, and continue to prompt the user until a default storage class exists.

Creating the default storage class might require installing the Local Storage Operator, LVMS, OpenShift Data Foundation, or another storage-related Operator.

Additionally, our postinstallation configuration docs mention storage. However, I think we need to prominently state that the user should create a default storage class, because many Operators will rely on a default storage class to make persistent volume claims. Without the ability to make persistent volume claims, the functionality will not work as advertised, generating errors and a bad user experience.

3. Why does the customer need this? (List the business requirements here)
To improve usability, we are pre-installing Operators and Operator bundles with the Assisted Installer. However, using these Operators often requires a default storage class–regardless of whether it's local storage, or a Ceph storage cluster. For example, every Operator that makes a Persistent Volume Claim will install just fine, but it will not work properly unless there is a default storage class. So users will find errors related to storage without necessarily knowing why the error is occurring if the error messages aren't helpful enough. This is not a good user experience. I encountered this while trying to install Red Hat Advanced Developer Suite.

4. List any affected packages or components.

Basically, every Operator that makes a persistent volume claim is affected if the end user starts trying to use an Operator that requires a PVC, but before installing a storage Operator and creating a default storage class.

Generally, I think this is a bad user experience–people expecting that an installed Operator will work as advertised, but not knowing that it requires a default storage class to work properly.