Closed arnavgup1 closed 5 months ago
Hi @arnavgup1. 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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: arnavgup1, seanzatzdev-amazon
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/ok-to-test
I have a question about the language added by this PR.
It seems that adding AmazonEFSCSIDriverPolicy
policy to the cluster's node group's IAM role is essentially the same as third method using instance profile policy:
If my node has AmazonEFSCSIDriverPolicy
on it, then any pod on that node can use it, regardless of EKS Pod Identity presence.
Am I missing something here?
Is this a bug fix or adding new feature? Feature
What is this PR about? / Why do we need it? Adds documentation for the Pod Identity feature used for customers that want to authenticate with the pod identity agent that is available through EKS Add-ons.
PR for the pod identity change: https://github.com/kubernetes-sigs/aws-efs-csi-driver/pull/1254