-
Notifications
You must be signed in to change notification settings - Fork 748
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
IAM Policy Doc Question #2985
Comments
We do mention it
|
Ah yes, you do. But the two policies differ and the cni pods are printing errors stating that permissions are missing. A mention of this error and confirmation that it's safe to ignore as long as you are not looking for automatic subnet discovery would have prevented me from opening this issue. Happy to submit a PR if this is correct. Or perhaps a better path would be to simply reference the managed policy as the authoritative source of policies required? Is that technically true? |
oh, I see. We should update the doc here - https://github.com/aws/amazon-vpc-cni-k8s/blob/master/docs/iam-policy.md with The doc exists to give over view of policies, and importantly how to scope down the policy. So, keeping it seems good. You could submit a PR with adding the ec2:DescribeSubnets to the doc. |
Thanks, i'll have a PR in tomorrow. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
What happened:
By following the iam policy guidelines linked in the readme, we receive the below error and appear to be missing some iam policies when compared to the aws managed policy.
Error message:
The additional permissions don't appear necessary in most situations, and because we tag subnets. But I was wondering if the aws managed policy AmazonEKS_CNI_Policy should be linked in the docs here or if there is other clarifying guidance on this error.
Environment:
kubectl version
): 1.29.4-eks-036c24bcat /etc/os-release
): N/Auname -a
): N/AThe text was updated successfully, but these errors were encountered: