https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
o
Seem rancher creates 2 launch templates. One without user-data and a second that configures the nodes but launches the first empty one... It's not clear how I would update the bootstrap args without breaking automation
I understand where 
rancher-managed-lt-%
comes from, that documented but I get a second launch template created that actually seems to configure nodes and runs the bootstrap script in the user-data. This seems automatically generated by rancher too so I don't really want to force user-data on the rancher managed lt. If I create a new version and apply to the AutoScale group to get the max pods value updated then Rancher complains that EKS isn't managing the launch template and therefore loases control
a
Rancher creates the launch template to configure the node group, but EKS is responsible for injecting the user data that bootstraps the node. You can add you own user data to the rancher-created launch template, but EKS will still inject its script.
6 Views
Open in Slack
PreviousNext
Powered by