You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought I understood this, but I'm now not sure I do...
The security groups are named uniquely (incorporating the cluster name). The security group rules do not incorporate the cluster name, but these are "virtual objects" - the name does not render into the AWS API.
I guess this would cause a problem if you took two TF cluster outputs, and rendered them both in the same TF run (e.g. by merging the directories). Is that how you are seeing the problem? And if not, how can I reproduce it?
Haven't heard anything here. I believe the problem must be when you have 2 kops-generated terraform output files, in the same TF "universe". Then the rules will have the same name.
I think this is the problem that modules are supposed to solve, so I am going to close as a duplicate of #1026, and also opened #1381
Closing, but if there's something else, let's reopen.
the resources "aws_security_group_rule" have a "default" name, which conflicts with other clusters created with terraform
The text was updated successfully, but these errors were encountered: