Feature Overview (aka. Goal Summary)  

In 4.13 STOR-990 we added support for EFS cross account where OCP and the actual EFS are in different account. We have reports that the procedure we provide to configure it does not work with ROSA.

The goal of this epic is to identify the gaps between self managed and ROSA, find solutions and document it in the ROSA documentation.

UPDATE:

After further investigation, it seems to be due to fact that the procedure we provide is difficult to follow and prone to errors. The goal of this feature is therefore to rewrite the cross account configuration procedure for standalone clusters including STS, non-STS and HCP configurations as well as having CI jobs that will follow the new procedure as closely as possible to ensure

Goals (aka. expected user outcomes)

rewrite the cross account configuration procedure for standalone clusters including STS, non-STS and HCP configurations as well as having CI jobs that will follow the new procedure as closely as possible to ensure

Requirements (aka. Acceptance Criteria):

Clear, understandable and straightforward documentation on how to configure cross account EFS. The doc can be reused by the ROSA team to be included in their documentation.

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 a ROSA customer i would like to access EFS data that is hosted in a different AWS account than the one used for OCP

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.

Out of Scope

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

Applies to EFS only

Background

In 4.13 STOR-990 we added support for EFS cross account where OCP and the actual EFS are in different account. We have reports that the procedure we provide to configure it does not work with ROSA.

UPDATE: the procedure we provide is difficult to follow and prone to errors.

Customer Considerations

Should be reused by the ROSA team to be included in their docs

Documentation Considerations

The full cross account EFS section should be revisited

backport all the way back to 4.14

Interoperability Considerations

Should be applicable to ROSA