Set correct userIDGroupPairs
defaults for SecurityGroups
CRs.
#194
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes aws-controllers-k8s/community#2068,
aws-controllers-k8s/community#2061, and
aws-controllers-k8s/community#2058
The EC2 API for setting ingress/egress rules has many special restrictions,
making its behavior hard to predict. For example,
GroupName
should only beused with default VPCs. When using non default VPCs users should use
GroupID
instead
To address this problem, we are introducing a defaulting mechanism to help the
controller infer and use the correct
GroupID
when a user doesnt provide one.You might wonder why all the trouble, and why not just use ACK resource references?
Well.. this is necessary because ACK resource references cannot do self
references, making fully declarative egress/ingress rule definition impossible in some
cases.
Changes:
UserIDGroupPairs.GroupName
as non-required (at the CRD level)UserIDGroupPairs.GroupID
to the parent security group IDUserIDGroupPairs.VPCID
to the VPC of the parent security groupUserIDGroupPairs
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.