Skip to content
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

Allow creating default instance role even when no default node group is created #1511

Merged
merged 3 commits into from
Dec 4, 2024

Conversation

flostadler
Copy link
Contributor

As part of #1176 we took the decision to not create the default instance role if users disable the default node groups. Our assumption back then was that there's not a substantial need for this role when users opt out of the default node groups.

#1510 has shown that there is indeed users that were relying on this default instance role that was created "by accident". This original change made the upgrade to v3 more painful than necessary for this set of users!

This change introduces a new plain flag createInstanceRole that can be used to opt-into creating the default instance role even when no default node group is needed.

Resolves #1510

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@flostadler flostadler self-assigned this Dec 4, 2024
Copy link

github-actions bot commented Dec 4, 2024

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@flostadler flostadler requested review from t0yv0, corymhall and a team December 4, 2024 15:33
@flostadler flostadler merged commit ae815c8 into master Dec 4, 2024
34 checks passed
@flostadler flostadler deleted the flostadler/createInstanceRole branch December 4, 2024 16:10
@bob-bins
Copy link

bob-bins commented Dec 4, 2024

Thanks a bunch @flostadler ! One nitpick is that docs/eks-v3-migration.md can be upgraded to mention createInstanceRole. Something like:

Previously the Cluster component created a default node IAM role even if skipDefaultNodeGroup was set to true. This role gets correctly omitted now if you are specifying skipDefaultNodeGroup. If you have skipDefaultNodeGroup set to true and would like to keep the node IAM role through the migration, you may set createInstanceRole to true.

@flostadler
Copy link
Contributor Author

Thanks a bunch @flostadler ! One nitpick is that docs/eks-v3-migration.md can be upgraded to mention createInstanceRole. Something like:

Previously the Cluster component created a default node IAM role even if skipDefaultNodeGroup was set to true. This role gets correctly omitted now if you are specifying skipDefaultNodeGroup. If you have skipDefaultNodeGroup set to true and would like to keep the node IAM role through the migration, you may set createInstanceRole to true.

Absolutely, I'm already working on the changes to the official docs that get published to https://www.pulumi.com/docs/ and will back-port those to here afterwards!

flostadler added a commit that referenced this pull request Dec 6, 2024
This adds docs for the `createInstanceRole` cluster option.

Relates to #1511
@pulumi-bot
Copy link
Contributor

This PR has been shipped in release v3.4.0.

flostadler added a commit to pulumi/registry that referenced this pull request Dec 9, 2024
This adds docs for the `createInstanceRole` cluster option.
Relates to pulumi/pulumi-eks#1511
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

instanceRole is no longer automatically created when skipDefaultNodeGroup: true
4 participants