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

[Feature] eksctl update accessentry to update already existing Access Entries #7842

Open
AmitBenAmi opened this issue Jun 18, 2024 · 1 comment
Labels
kind/feature New feature or request priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@AmitBenAmi
Copy link
Contributor

What feature/behavior/change do you want?

eksctl update accessentry that will update existing Access Entries with new properties.

The aws eks cli already support this API with some options - https://docs.aws.amazon.com/cli/latest/reference/eks/update-access-entry.html

Why do you want this feature?

I find multiple use-cases of updating an existing Access Entry, such as:

  • Adding another kubernetesGroup
  • Adding another namespace to the scoped namespaces
  • Adding another Access Policy

Today it either needs to be done:

  1. aws cli
  2. AWS Console
  3. Delete and Re-Create the Access Entry, which might cause downtime
@AmitBenAmi AmitBenAmi added the kind/feature New feature or request label Jun 18, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jul 19, 2024
@TiberiuGC TiberiuGC added priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases and removed stale labels Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Development

No branches or pull requests

2 participants