We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For more details, see Upcoming Changes to IP Assignment for EKS Managed Node Groups.
It seems like I would just need to add the property MapPublicIpOnLaunch: true to all the subnets in the vpc.yml template:
MapPublicIpOnLaunch: true
vpc.yml
Subnet1a: Type: AWS::EC2::Subnet Properties: VpcId: !Ref VPC AvailabilityZone: Fn::Sub: '${Region}a' CidrBlock: 172.16.0.0/18 # This is the new setting: MapPublicIpOnLaunch: true Tags: - Key: Name Value: eks-example-a
The text was updated successfully, but these errors were encountered:
Confirmed that this worked out correctly in the end. Will make this update in the next version of the book.
Sorry, something went wrong.
44000a7
No branches or pull requests
For more details, see Upcoming Changes to IP Assignment for EKS Managed Node Groups.
It seems like I would just need to add the property
MapPublicIpOnLaunch: true
to all the subnets in thevpc.yml
template:The text was updated successfully, but these errors were encountered: