Terraform-provider-aws: eks-getting-started guide is broken

Created on 28 Apr 2020  ·  11Comments  ·  Source: hashicorp/terraform-provider-aws

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.12.24
+ provider.aws v2.59.0
+ provider.http v1.2.0

Affected Resource(s)

  • examples/eks-getting-started guide

Terraform Configuration Files

This is in the examples/eks-getting-started guide

Expected Behavior

Guide does not crash

Actual Behavior

I get the following

Error: error waiting for EKS Node Group (terraform-eks-demo:demo) creation: Ec2SubnetInvalidConfiguration: One or more Amazon EC2 Subnets of [subnet-053f0598226074145, subnet-0badf4770adfbb0ba] for node group demo does not automatically assign public IP addresses to instances launched into it. If you want your instances to be assigned a public IP address, then you need to enable auto-assign public IP address for the subnet. See IP addressing in VPC guide: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html#subnet-public-ip. Resource IDs: [subnet-053f0598226074145 subnet-0badf4770adfbb0ba]

  on eks-worker-nodes.tf line 41, in resource "aws_eks_node_group" "demo":
  41: resource "aws_eks_node_group" "demo" {

Steps to Reproduce

  1. git clone 'https://github.com/terraform-providers/terraform-provider-aws.git'
  2. cd terraform-provider-aws/examples/eks-getting-started
  3. terraform init
  4. terraform apply
  5. type yes and click enter
  6. See that it fails
serviceks

Most helpful comment

The fix to include the map_public_ip_on_launch = true argument in examples/eks-getting-started has been merged.

All 11 comments

Got it, I just thought the guide should be updated because as of right now it doesn't work

Hi,

I set map_public_ip_on_launch = True, no change.

As Daniel mentioned above, after this improvement I started getting the error. Besides, I would like to deploy my k8s worker nodes without public IP.

Best,

@JesterOrNot , @thewizardofoz I still can not figure out how to fix this problem, is there any help?

I also have this problem and no fix for it yet. Any advice?

@sveba I do not have any good solution for this but now I am using Gcloud provider and everything seems good so far (https://github.com/sexydevops/terraform-googlecloud-kubernetes)

Hi,

I set map_public_ip_on_launch = True, no change.

As Daniel mentioned above, after this improvement I started getting the error. Besides, I would like to deploy my k8s worker nodes without public IP.

Best,

Try running terraform plan and then terraform apply. It worked for me after making that change. not sure if terraform is case sensitive but I used true instead.

The fix to include the map_public_ip_on_launch = true argument in examples/eks-getting-started has been merged.

Anyone had the same exception after the new update?
error waiting for EKS Node Group (terraform-eks-demo:demo) creation: NodeCreationFailure: Instances failed to join the kubernetes cluster.

This has been released in version 2.63.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 for triage. Thanks!

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

Was this page helpful?
0 / 5 - 0 ratings