Allow negation of interfaces for iptables rules#320
Open
gjtempleton wants to merge 1 commit intojtblin:mainfrom
Open
Allow negation of interfaces for iptables rules#320gjtempleton wants to merge 1 commit intojtblin:mainfrom
gjtempleton wants to merge 1 commit intojtblin:mainfrom
Conversation
gjtempleton
force-pushed
the
Allow-Negation-Of-Interfaces
branch
from
7f82e5b to
d94b75a
Compare
Based on matching functionality in Kiam Introduced by uswitch/kiam#54
gjtempleton
force-pushed
the
Allow-Negation-Of-Interfaces
branch
from
d94b75a to
75ba9b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this PR does / why we need it:
As per the AWS docs for AWS VPC CNI security groups per pod, pods using security groups per pod will be assigned
vlan*interfaces on the nodes, noteni*interfaces as with pods not making use of this functionality. This means that currently kube2iam can either be set up to capture IAM traffic from pods making use of security groups per pod, or those not using it, but not both, unless you pass the interface as+, thus capturing all EC2 metadata traffic for the entire host.Based on existing functionality to allow negative matching of interfaces in uswitch/kiam introduced by uswitch/kiam#54
Which issue this PR fixes
Special notes:
Checklist chart
N/A