EKS-Getting-Started page is outdated

[cazorla19]

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 "me too" comments, 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

Doesn't matter, it's about the docs

Affected Resource(s)

• aws_eks_cluster and its components

Terraform Configuration Files

I'm reporting about EKS Getting Started Guide as a documentation component.

What are the problems about:

1. Community AMI name prefix has been changed from eks-worker-* to amazon-eks-node-*

2. Userdata for get the node joining cluster is totally different. Instead of making script itself you just need to run the built-in-image script. Smth like:

#!/bin/bash -xe

# Bootstrap and join the cluster
/etc/eks/bootstrap.sh --b64-cluster-ca '${cluster_auth_base64}' --apiserver-endpoint '${endpoint}' --kubelet-extra-args '${kubelet_extra_args}' '${cluster_name}'

User adjust might not be clear, and time for cluster setup will be mostly wasted. So, I'll personally rewrite infrastructure, leaving this issue mostly for history and PR attachment.

Expected Behavior

EKS cluster is up and running with no need to connect and debug EC2 instances.

Actual Behavior

Terraform couldn't find the latest AMI image and reports an error.

After fixing issue #1: nodes can actually join the cluster, but DNS configuration is hecked up, so the deployments will not properly work on cluster by missing cluster-dns settings.

Steps to Reproduce

Just go through this guide again from scratch.

Important Factoids

Nothing special for account/resource, issue is common for everybody.

[cazorla19]

Please, assign me to the issue.

[bflad]

Hi @cazorla19 👋 Did you already have something written up? I started this yesterday as part of #5483 and we have an immediate need to release an update today.

[cazorla19]

@bflad oh, I've checked your commit and it seems like you're doing the same thing I'd like to! Then this issue doesn't make sense. Sorry for confusion, I'll close it and track your today release then :)

[bflad]

@cazorla19 no worries! Thanks for your interest in fixing the documentation! 😄

[ghost]

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!