[EKS] [request]: Provide list/get nodes permissions to AmazonEKSAdminPolicy
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
AmazonEKSAdminPolicy should have permissions to list/get nodes.
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
This is useful to check what nodes are part of the system and accordingly they can be managed. It helps users with limited admin access to check status of nodes and request users with wider access to help fix the issues.
**Are you currently working around this issue?**
Provide `AmazonEKSClusterAdminPolicy` access to those who want to only see the nodes
Contributor guide
Research direction
Start by reviewing the AmazonEKSAdminPolicy permissions and the EKS request details in this issue. Determine the permissions needed to list and get nodes, then confirm that the policy lets limited administrators inspect node status without granting the broader AmazonEKSClusterAdminPolicy access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- authorization, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100