I’m following the instructions from the Provision an EKS Cluster (AWS) tutorial.
git clone https://github.com/hashicorp/learn-terraform-provision-eks-cluster
aws eks --region $(terraform output region) update-kubeconfig --name $(terraform output cluster_name)
Provided region_name '"us-east-2"' doesn't match a supported format.
- Easily resolved by providing parameters directly:
aws eks --region 'us-east-2' update-kubeconfig --name 'training-eks-orAxPAav'
- But nicer if this just worked.
- First problem:
- I follow the rest of the examples, metrics server, dashboard, authenticating. All work fine.
- Last step:
During the destroy, terraform-destroy.out.txt (100.7 KB), things just stop somewhere in the middle and I get this on stderr:
I do a second
terraform destroy, terraform-destroy-2.out.txt (40.1 KB). More things get destroyed but again stops in the middle with
Error: Unauthorized on stderr.
I do a third
terraform destroy and this time it halts immediately, terraform-destroy-3.out.txt (3.8 KB). With this on stderr:
Error: Delete "http://localhost/api/v1/namespaces/kube-system/configmaps/aws-auth": dial tcp [::1]:80: connect: connection refused
Any further attempts to destroy end the same way.
As a workaround, I manually remove the offending resource from the state:
$ terraform state rm module.eks.kubernetes_config_map.aws_auth Removed module.eks.kubernetes_config_map.aws_auth Successfully removed 1 resource instance(s).
After that, a final destroy succeeds with 0 resources destroyed.
Could this be a bug in terraform or the eks module or is there a better example I could be following as a basis for my first Terraform-managed EKS environemnt?