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 negation of interfaces for iptables rules #320

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gjtempleton
Copy link

@gjtempleton gjtempleton commented Aug 10, 2021

What this PR does / why we need it:

  • Allows negation of interfaces in iptables rules

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, not eni* 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

@gjtempleton gjtempleton force-pushed the Allow-Negation-Of-Interfaces branch from 7f82e5b to d94b75a Compare August 10, 2021 23:32
Based on matching functionality in Kiam
Introduced by uswitch/kiam#54
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.

EKS security groups for pods
1 participant