-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Bug]: EKS cluster ID is not always cluster name #27560
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v4.45.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.3.3
AWS Provider Version
4.37.0
Affected Resource(s)
aws_eks_cluster
Expected Behavior
The computed output for
id
should be pulled from thedescribe-cluster
API when present, otherwise fallback to current behavior of using the cluster nameSpecifically, if you provision a local cluster on AWS Outposts, the cluster ID will NOT match the cluster name and instead look like a UUID/GUID
Actual Behavior
All clusters created, the computed ID is set to the cluster name per
terraform-provider-aws/internal/service/eks/cluster.go
Line 345 in 990f9ae
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
An example can be found here https://github.com/bryantbiggs/terraform-aws-eks/tree/refactor/v19/examples/outposts
Steps to Reproduce
AWS CLI
Commercial regions with EKS cluster provisioned on AWS:
Will return
null
Local cluster provisioned on AWS Outposts (both control plane and data plane):
Should return a value that looks like a UUID/GUID value
Terraform
Minimal reproduction using and updated version of this test case. Note, this will result in an
Unauthorized
error since the--cluster-id
passed is the cluster name. Once corrected in the provider, this should apply successfully without modificationDebug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: