Provision the EKS cluster and join the worker nodes without using Kubectl

[dhineshbabuelango]

Hi All,
We are using terraform to provision EKS. Once the EKS master and worker nodes are provisioned through terraform, we will run a kubectl command to create a config map aws-auth to enable worker nodes to join your cluster. Can this be achieved in terraform itself without running any kubectl commands.

[max-rocket-internet]

Yes, it's already done automatically by this module.

[dhineshbabuelango]

Hi Max, it’s automatically done?
Could you please give me more details if possible. On which module?
Thanks again for your reply.

[max-rocket-internet]

In here: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/aws_auth.tf

[dhineshbabuelango]

Thanks Max, I tried it is working. But when we provision a new EKS cluster with only private endpoint enabled, will we be still able to apply the aws-auth config map. Since we are running terraform from our local and EKS endpoint will not be resolved outside of its VPC, with only private endpoint enabled, will we be able to run the aws-auth configmap

[max-rocket-internet]

when we provision a new EKS cluster with only private endpoint enabled, will we be still able to apply the aws-auth config map

Nope 🙂

[dhineshbabuelango]

Thanks Max, so we can run aws-auth config map for private endpoint only enabled EKS cluster, if we run the terraform scripts inside a ec2 instance which is running in the same VPC as EKS cluster

[max-rocket-internet]

Exactly. Terraform is running kubectl, kubectl needs to auth and connect to the EKS API endpoint. You can make that happen by running Terraform from within your VPC, or using a VPN, or SSH tunnelling etc.

[max-rocket-internet]

Sorry, I didn't mean to close the issue so feel free to reopen it 🙂

[dhineshbabuelango]

Thanks Max, that answered my question :)

[github-actions]

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.