1. Proposed title of this feature request

Alias/link for StorageClass names to keep StorageClass naming between different OpenShift installations.

2. What is the nature and description of the request?

OpenShift can be installed with storage in several ways. For example:

• OpenShift with Internal OpenShift Data Foundation.
• OpenShift with External Ceph.
• OpenShift on OpenStack (using OpenStack storage).
• ...

In all cases, the StorageClass name will be different. It could be interesting to have a way to use generic names for the StorageClasses provided, so the application deployments can use the generic name of the StorageClass instead pointing to the original StorageClass name.

3. Why does the customer need this? (List the business requirements here)

The deployment of applications with dynamic PersistentVolumeClaims depends on the StorageClass name. As this name varies, the deployments need to be manually changed to accommodate different names between clusters, depending on which storage is using the application. By having the choice to use generic StorageClass names, the applications could use a unified deployment for their applications between different OpenShift clusters.

The available workaround as of now consists in manually creating separate storage classes with the same specs as the existing ones, but with the desired names. However, having duplicate storage classes simply because the names of the default ones are different between different OpenShift clusters, doesn't seem to be a good approach.

4. List any affected packages or components.

OpenShift Storage