-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[PrivateLink Access] Tracking issue to update this pattern when cluster access with EKS API is released #1816
Comments
This issue has been automatically marked as stale because it has been open 30 days |
IAM Cluster Access Management has been released. Will work on updating the blueprint shortly. cc: @vchintal @praseedasathaye |
we'll be able to update once terraform-aws-modules/terraform-aws-eks#2858 lands |
This issue has been automatically marked as stale because it has been open 30 days |
Working on it this week. |
Description
The PrivateLink Access pattern initially creates the EKS cluster with a public endpoint. This is done to allow Terraform to add an IAM role to the
aws-auth
ConfigMap. The cluster endpoint is then manually set to private.This issue is a reminder to update the pattern when the Cluster Access roadmap feature is released. At this point in time, it's labeled as "Coming Soon"
The updated pattern will initially set the cluster endpoint as private and use new EKS API capabilities to add the IAM role acces to the Kubernetes cluster.
The text was updated successfully, but these errors were encountered: