Epic Goal*

What is our purpose in implementing this?  What new capability will be available to customers?

Have Zonal volume support for the AWS EFS CSI driver + operator.

This appears to require python3-botocore package in order to fall back to DescribeMountTargets when file system DNS resolution fail. This package does not exist in RHEL so we need to find the best way to pull it in.

The goal is to get on par with upstream CSI driver. There may be still cases where the zonal volumes will be unusable, we need to ensure they are properly documented.

 
Why is this important? (mandatory)

What are the benefits to the customer or Red Hat?   Does it improve security, performance, supportability, etc?  Why is work a priority?

Numerous customers are asking for this capability. See RFE-4745

 
Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

1. When DNS resolution fails the CSI driver should fall back to DescribeMountTargets and continue to work

 
Dependencies (internal and external) (mandatory)

What items must be delivered by other teams/groups to enable delivery of this epic. 

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - 
• Documentation -
• QE - 
• PX - 
• Others -

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

Driver is able to  fall back to DescribeMountTargets when file system DNS resolution fail

Drawbacks or Risk (optional)

Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

Since python3-botocore is not in RHEL, pulling it in and maintaining it add extra load on the team.

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”