Skip to content
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

[EKS] [request]: Manage aws-auth ConfigMap in AWS Console #1278

Closed
lnalex opened this issue Feb 17, 2021 · 5 comments
Closed

[EKS] [request]: Manage aws-auth ConfigMap in AWS Console #1278

lnalex opened this issue Feb 17, 2021 · 5 comments
Assignees
Labels
EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue

Comments

@lnalex
Copy link

lnalex commented Feb 17, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction 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
What do you want us to build?

Add a feature to allow customers to manage and configure the aws-auth ConfigMap for an EKS cluster directly from the AWS Management Console.

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?
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.

Make it easier for customers to get started with EKS clusters from the AWS Console, particularly when using different roles for Console and CLI access. This would also make managing clusters from the AWS Console a more complete experience.

Are you currently working around this issue?
How are you currently solving this problem?

N/A

Additional context
Probably related to/requires implementation of the underlying API to manage aws-auth:
#185 (comment)

Attachments
N/A

@lnalex lnalex added the Proposed Community submitted issue label Feb 17, 2021
@mikestef9 mikestef9 added the EKS Amazon Elastic Kubernetes Service label Feb 17, 2021
@mikestef9 mikestef9 self-assigned this Feb 17, 2021
@vennemp
Copy link

vennemp commented Mar 10, 2021

At the very least allow an option to add an additional iam principal to the system:masters group at cluster launch.

@siqusoft
Copy link

siqusoft commented Apr 22, 2021

This is one of bottle neck for enterprises where single aws account managed by multiple teams with different responsibilities. As a developer, you may not assume automation execution roles for security reasons and it is very difficult to get access to the cluster you just created with out going through a lot of hustles or with out writing a lot of automation to accomplish this. it would be best handle by aws in native way.

@mikestef9
Copy link
Contributor

This will be solved by #185

@siqusoft
Copy link

This will be solved by #185

Thanks @mikestef9! do we have any ETA?

@mikestef9
Copy link
Contributor

Addressed with #185

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue
Projects
Status: Shipped
Development

No branches or pull requests

4 participants