-
Notifications
You must be signed in to change notification settings - Fork 80
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
Do not create instance role when skipDefaultNodeGroup
is enabled
#1411
Do not create instance role when skipDefaultNodeGroup
is enabled
#1411
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. |
sdk/python/pulumi_eks/_inputs.py
Outdated
@@ -289,7 +289,7 @@ class ClusterNodeGroupOptionsArgsDict(TypedDict): | |||
|
|||
Note: Given the inheritance of auto-generated CF tags and `cloudFormationTags`, you should either supply the tag in `autoScalingGroupTags` or `cloudFormationTags`, but not both. | |||
""" | |||
bootstrap_extra_args: NotRequired[str] | |||
bootstrap_extra_args: NotRequired[pulumi.Input[str]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we missing CI check guarantees that the worktree should be clean possibly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're merging those into a feature branch that's only built when cutting an alpha release or when triggered manually. It's checking it as part of those workflows
docs/eks-v3-migration.md
Outdated
|
||
### Cluster does not create extraneous instance IAM role if `skipDefaultNodeGroup` is set to `true` | ||
|
||
Previously the Cluster component created a default instance IAM role even if `skipDefaultNodeGroup` was set to `true`. This role gets correctly omitted now if you're specifying `skipDefaultNodeGroup`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"if you are"
When enabling
skipDefaultNodeGroup
we should not be creating resources related to the default node group. This includes the default instance role.With this change the
Cluster
component will no longer create this default role whenskipDefaultNodeGroup
is enabled.One of the tests needs re-recording because we're introducing a breaking change (i.e. not creating the extraneous instance role), but in doing so we're aligning the provider with user expectations. Once this is merged in I'll release the next version and re-record.
Fixes #1176