aws / aws/containers-roadmap

[EKS][request]: extend AmazonEKSLoadBalancingClusterPolicy to support EKS Auto Mode

Open
#2,851 0 comments 0 reactions 0 assignees View on GitHub
EKS EKS Auto Mode Proposed
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**

Add `create`/`update`/`delete` on `ingressclasses.networking.k8s.io` and
`ingressclassparams.eks.amazonaws.com` to `AmazonEKSLoadBalancingClusterPolicy`
(currently `get`/`list`/`watch` only).

**Which service(s) is this request for?**

EKS (Access Entries / Auto Mode)

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

We want an AWS-provided EKS access policy that lets a customer principal manage IngressClass/IngressClassParams for EKS Auto Mode's built-in ALB controller, without granting `AmazonEKSClusterAdminPolicy`. `AmazonEKSLoadBalancingClusterPolicy` does not allow this.

**Are you currently working around this issue?**

`AmazonEKSClusterAdminPolicy`, or custom `ClusterRole`/`ClusterRoleBinding`.

**Additional context**

N/A

**Attachments**

N/A

Contributor guide

Open the contributing guide

Research direction

Start with the requested AmazonEKSLoadBalancingClusterPolicy change and the EKS Auto Mode resources named in the issue: ingressclasses.networking.k8s.io and ingressclassparams.eks.amazonaws.com. Compare the current get/list/watch permissions with the requested create/update/delete permissions, and consider the stated goal of avoiding AmazonEKSClusterAdminPolicy. Done means AWS provides the requested scoped access policy.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
authorization, cloud, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.