-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc: Access Points: Require separate file systems #168
Conversation
Hi @2uasimojo. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Per [issue kubernetes-sigs#167](kubernetes-sigs#167), it turns out that you *can't* use separate access points to the same EFS volume from the same pod. Correct the documentation pending a fix.
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 2uasimojo, leakingtapan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-aws-efs-csi-driver-e2e |
/test pull-aws-efs-csi-driver-verify |
Per issue #167, it turns out that you can't use separate access points to the same EFS volume from the same pod. Correct the documentation pending a fix.
Is this a bug fix or adding new feature?
Docs only.
What is this PR about? / Why do we need it?
Docs are wrong until #167 is resolved.
What testing is done?
Rendered doc. Looks peachy.