[EKS] [request]: branch ENI tagging - SG for PODs
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
When using SG for PODS, an ENI gets attached to each POD.
AWS Network Firewall supports tag-based filtering with ENIs as resources.
This request is to enable ENI tagging by the VPC CNI by the use of annotations so that AWS Network Firewall can leverage those to filter traffic.
Tags could be things like:
namespace
VPC ID
subnet ID
Security Group ID
custom tags specified by user in annotations
**Which service(s) is this request for?**
This could be EKS with VPC CNI
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Customers would like the ability to create outbound L7 filtering policies based on which pod(s) they are originated from.
i.e. I would like pods from a certain deployment to only be able to do HTTPs towards a specific URL.
Today VPC CNI does not allow that (not in the `NetworkPolicy` K8s spec. The use of different CNIs (i.e. Cilium) has significant challenges and does not support security-groups per pod.
**Are you currently working around this issue?**
We are not.
**Attachments**
Original issue: https://github.com/aws/amazon-vpc-resource-controller-k8s/issues/333
Contributor guide
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing the referenced original issue in aws/amazon-vpc-resource-controller-k8s and the VPC CNI and AWS Network Firewall requirements; done means annotations can produce ENI tags that support the requested pod-origin filtering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100