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

fix(nodeSecurityGroupTags): only expose option through Cluster class #126

Merged
merged 3 commits into from
May 9, 2019

Conversation

metral
Copy link
Contributor

@metral metral commented May 3, 2019

Fixes #125.
Related #122.

Update for the new tag opts (based on orig in #122):

  • New options per class:
    • Cluster class:
      • .tags - A map of tags that is applied to all AWS resources under management by a pulumi/eks cluster. Currently applied to: eksClusterSecurityGroup, nodeSecurityGroup, the Worker AutoScalingGroup (ASG), and cloudFormation stack.
      • .clusterSecurityGroupTags - A map of tags applied to the EKS Cluster security group
      • .nodeSecurityGroupTags - A map of tags applied to the Worker Nodes security group
    • NodeGroup class:
      • .cloudFormationTags - A map of tags applied to the CloudFormation Stack of Worker Nodes
      • .autoScalingGroupTags - A map of tags applied to the Worker NodeGroup ASG & Instances
      • Note:
        • If you create & pass in an external nodeSecurityGroup, you can tag it by manually setting the tags during its external creation, and before it is used in the NodeGroup.

@metral metral changed the title Fix nodeSecurityGroup tags fix(nodeSecurityGroupTags): only expose option through Cluster class May 3, 2019
metral added a commit that referenced this pull request May 3, 2019
@metral metral force-pushed the metral/fix-nodeSecurityGroupTags branch from 908859e to 2b5409b Compare May 3, 2019 21:52
metral added a commit that referenced this pull request May 3, 2019
@metral metral requested a review from lukehoban May 3, 2019 21:58
Copy link
Member

@lukehoban lukehoban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

*
* Note: If you want to tag this `nodeSecurityGroup`, you must manually
* tag it during its external creation, before it is used in this node
* group.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps phrase this as nodeSecurityGroup and nodeSecurityGroupTags are mutually exclusive? We could also test that at most one is set and error.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lukehoban both the option comment, and the mutual exclusion check have been addressed. PTAL

@metral metral force-pushed the metral/fix-nodeSecurityGroupTags branch from 2b5409b to aad56f0 Compare May 9, 2019 00:05
metral added a commit that referenced this pull request May 9, 2019
@metral metral force-pushed the metral/fix-nodeSecurityGroupTags branch from aad56f0 to c1cd2c3 Compare May 9, 2019 00:07
@metral metral modified the milestone: 0.23 May 9, 2019
Copy link
Member

@lukehoban lukehoban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@metral metral merged commit 0884a1c into master May 9, 2019
@pulumi-bot pulumi-bot deleted the metral/fix-nodeSecurityGroupTags branch May 9, 2019 17:07
flostadler pushed a commit that referenced this pull request Sep 4, 2024
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.

nodeSecurityGroupTags is not being applied when provided in a NodeGroup
2 participants