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

[Docs]: AWS EKS Access Entries setting bootstrap_cluster_creator_admin_permissions is not set to true by default #36259

Open
gygitlab opened this issue Mar 7, 2024 · 2 comments
Labels
documentation Introduces or discusses updates to documentation. service/eks Issues and PRs that pertain to the eks service.

Comments

@gygitlab
Copy link

gygitlab commented Mar 7, 2024

Documentation Link

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_cluster#bootstrap_cluster_creator_admin_permissions

Description

The documentation suggests that the AWS EKS Access Entries setting bootstrap_cluster_creator_admin_permissions is set to true by default, matching what happens in the AWS console.

This isn't the case. As a result if this setting is missed new AWS EKS clusters are not configured to allow admin access for the Principal that creates the cluster.

The docs also don't mention the clash that happens subsequently with this setting but this has already been raised separately - ignore_changes is required basically.

References

https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html

Would you like to implement a fix?

No

@gygitlab gygitlab added the documentation Introduces or discusses updates to documentation. label Mar 7, 2024
Copy link

github-actions bot commented Mar 7, 2024

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Mar 7, 2024
@justinretzolk justinretzolk added service/eks Issues and PRs that pertain to the eks service. and removed needs-triage Waiting for first response or review from a maintainer. labels Mar 7, 2024
@mohammed-bachrouch
Copy link

mohammed-bachrouch commented Apr 19, 2024

I noticed this issue as well. It caused me to take down an entire cluster and re-create it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Introduces or discusses updates to documentation. service/eks Issues and PRs that pertain to the eks service.
Projects
None yet
Development

No branches or pull requests

3 participants