-
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
Possibility to set preBootstrapCommands when using custom ami with managed nodegroups #4032
Comments
Is this a bug? eksctl docs/examples state this is possible: https://eksctl.io/usage/schema/#managedNodeGroups-preBootstrapCommands Tracking the code base, it appears that makeCustomAMIUserData (https://github.com/weaveworks/eksctl/blob/main/pkg/nodebootstrap/managed_al2.go#L38) only respects the OverrideBootstrapCommand function (not preBootstrap): |
the example from aws blog is not valid; overrideBootstrapCommand is not a sub-key of preBootstrapCommands. |
You're right, @kishoregv, additionally, as @tanvp112 noted, the example in the AWS blog post is incorrect, |
Agree, did not go with it literally I have considered the indentation issue in my test. I should have already called it out in my issue report. |
What feature/behavior/change do you want?
When pinning AMI for a managed nodegroup, currently eksctl ignores preBootstrapCommands. It would nice to have preBoostrapCommands.
AWS blog talks about the workflow with eksctl, but eksctl does not respect preBootstrapCommands when using custom AMI.
Why do you want this feature?
This will allow us to do additional configuration before bootstrapping.
The text was updated successfully, but these errors were encountered: