-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create subnets with resource based hostnames #1455
Labels
Comments
this will be added in v4 here terraform-aws-modules/terraform-aws-vpc#838 |
this is now supported in v4.0.0 of the VPC module |
and this should now be available in EKS awsdocs/amazon-eks-user-guide#722 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Community Note
What is the outcome that you are trying to reach?
Subnets created with blueprints should use resource based names for instances. This will allow Kubernetes nodes to have names that reflect their names in ec2 instead of the private IPv4 addresses
More info here https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-naming.html
Describe the solution you would like
Creating a subnet with blueprints has this option enabled or exposed for customers. Examples should be updated to use this setting.
Describe alternatives you have considered
Changing hostnames in userdata or after the node is provisioned is not as consistent as doing it at the subnet level.
Additional context
This is a fairly new feature via aws/containers-roadmap#1723
The text was updated successfully, but these errors were encountered: