Closed jacekgajek closed 7 months ago
you need to provide the IAM entities the ability to access the cluster using cluster access entries
enable_cluster_creator_admin_permissions = true
fixed this.
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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
I used to manually create all EKS resources and recently I tried ot use the "eks" module. Since then, I cannot use
kubectl
CLI.For example
Returns
Previously, when I created EKS directly with terraform code I didn't have this problem. Same with AWS console, I also got an error "pods is forbidden".
I run terraform with the following creds:
and have my credentials stored in .aws/terraform
Expected behavior
When role terraform is assumed, pods can be accessed
Actual behavior
Forbidden error
Code
module parameters: