EFS Cross Account documentation revamp proposal

[RomanBednar]

Is your feature request related to a problem?/Why is this needed

The current documentation for configuring Cross Account feature is not very specific and has not been updated in a while. In OpenShift we provided customers with a slightly more detailed guide, however we've still had issue reports because users struggled to configure this feature.

/feature

Describe the solution you'd like in detail

In OpenShift 4.20 we're working on complete documentation revamp for this feature and it would be great if we had feedback from upstream as well. Eventually this could be reused in the upstream docs so we can be in sync.

Describe alternatives you've considered

None.

Additional context

Tested on Standalone cluster with and without STS. Static provisioning was not added to our docs in scope of this work.

[anthotse]

Hey @RomanBednar, are the instructions given in this blog post sufficient? Or are you suggesting for something more detailed?

https://aws.amazon.com/blogs/storage/mount-amazon-efs-file-systems-cross-account-from-amazon-eks/

[RomanBednar]

Hello @anthotse, we had something similar in OpenShift and figured it's not detailed enough for users to follow the instructions easily. So the suggestion is basically what you said - to have something more detailed.

The guide you linked is great but does not explain much and assumes quite a bit of AWS knowledge and some features ale left out, for example STS enabled clusters where there's different step needed we could have a clear distinction like this: https://github.com/openshift/csi-operator/pull/401/files#diff-5c4f1f33bb4c41d6c3e57b67e95dc097ebf581e3fdc2f5bbf848f15135179035R221

The permissions and roles might also need a review/update.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten