Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

In the corporate structure each department might have their own Azure subscription. The goal of this feature is to allow OCP to consume storage that are managed by another Azure subscription that the one used for OCP.

This applies to self managed and ARO

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

Customers should be able to consume Azure File storage that are outside it own Azure subscription. This is similar to what we did with AWS EFS https://issues.redhat.com/browse/RFE-2871

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

Make sure the driver supports it. The Azure doc seems to indicate this is the case

https://learn.microsoft.com/en-us/azure/aks/azure-files-csi#use-a-persistent-volume-with-private-azure-files-storage-private-endpoint
https://learn.microsoft.com/en-us/azure/private-link/how-to-approve-private-link-cross-subscription

We need to confirm if this is a test/doc only feature or if this indeed requires driver or operator dev work.

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):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

 any customer to use their own storage accounts with their applications deployed on centrally-managed Openshift platform

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Check with everything is implemented in the CSI driver and if there is any operator work needed.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

Limited to azure file

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

We implemented a similar RFE for AWS EFS, it seems fair to be consistent with Azure.

https://issues.redhat.com/browse/RFE-2871

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Provide all prep-work steps / dependencies and limitations if any

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

Document the full procedure

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

Benefits ARO where a managed OCP cluster could consume storage from a different Azure subscription that is not ARO managed.