Feature Overview (aka. Goal Summary)  

In some environments OCP and the storage are not deployed with the same subscription. This is particularly true with ARO. Cross sub access allows an OCP cluster in one subscription to consume storage that live in another sub.

Goals (aka. expected user outcomes)

Test and document cross subscription access with Azure File CSI. This is a testonly feature, the CSI driver already supports it.

This feature covers only subscription that are part of the same Azure tenant.

Requirements (aka. Acceptance Criteria):

The e2e tests muss pass the same way it does with single subscription

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

As an OpenShift admin I have an ARO cluster that is running on a different subscription than my Azure File data/service and I would like my ARO cluster to consume it.

Questions to Answer (Optional):

Is this testonly? Yes

Same tenant or different tenants? Start with same tenant / confirm if multi tenant is required.

Out of Scope

Subscriptions in different Azure tenants

Background

We already have implemented a similar RFE for EFS - STOR-990

Customer Considerations

Procedure may be complex and error prone, make sure the docs are extremely clear

Documentation Considerations

Be clear on the fact that this is limited to sub in the same tenant

Clearly document the different steps like we did for EFS

https://docs.openshift.com/container-platform/4.18/storage/container_storage_interface/persistent-storage-csi-aws-efs.html#persistent-storage-csi-efs-cross-account_persistent-storage-csi-aws-efs

Interoperability Considerations

Azure/ARO only