Your current user or role does not have access to Kubernetes objects on this EKS cluster

Your current user or role does not have access to Kubernetes objects on this EKS cluster

Solution: add your user (userarn) into aws-auth ConfigMap, you can use manage_aws_auth_configmap and aws_auth_users if using Terraform EKS module

• https://aws.amazon.com/premiumsupport/knowledge-center/eks-kubernetes-object-access-error/

This may be due to the current user or role not having Kubernetes RBAC permissions to describe cluster resources or not having an entry in the cluster’s auth config map. Learn more

Read: https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting_iam.html#security-iam-troubleshoot-cannot-view-nodes-or-workloads

1) eks:AccessKubernetesApi
2) aws-auth 
3) rolebinding

Related

• kubernetes_config_map_v1_data
• Terraform EKS module

See also

• AWS IAM Authenticator for Kubernetes: aws-auth, kubectl edit -n kube-system configmap/aws-auth, eksctl create iamidentitymapping, mapUsers:, mapRoles:, mapAccounts:
• EKS, eksctl, EKS add-ons, Amazon EKS cluster role, Terraform EKS, Kubernetes Autoscaler, Karpenter, Terraform module: EKS, Terraform resource: aws eks node group, Terraform data source: aws_eks_cluster, AWS Controllers for Kubernetes, AWS Load Balancer Controller, Amazon EKS Anywhere, Kustomize, aws-iam-authenticator, ACK, tEKS, Amazon EKS authorization, Amazon EKS authentication, Nodegroup, EKS storage, aws-ebs-csi-driver, aws-efs-csi-driver, aws-load-balancer-controller, amazon-vpc-cni-k8s, EKS security, EKS Best Practices Guides, hardeneks, EKS versions, fargate-scheduler, eks-connector, Resilience in Amazon EKS, EKS control plane logging