[EKS] [Feature Request]: Option to log all network flows to Cloudwatch without writing NetworkPolicies #2450
Labels
EKS Networking
EKS Networking related issues
EKS
Amazon Elastic Kubernetes Service
Proposed
Community submitted issue
Community Note
Tell us about your request
I would like to propose a flag within the advanced configuration options to capture all network traffic without a network policy. Add the ability for the node-agent to listen and log all network flows to cloudwatch.
Which service(s) is this request for?
EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
This would allow a user to have full visibility into not just traffic that occurs on a VPC within AWS but also traffic that happens within a cluster and within a node of that cluster.
Are you currently working around this issue?
A workaround I have found for now is to apply a network policy that allows all traffic in all namesspaces. This way the node-agent logs all flows as enforcement events and logs them to cloudwatch.
The problem is then if I want to apply a network policy limiting traffic between 2 specific pods then I must reapply this same policy in every namespace but the namespace those 2 pods reside in. As policies become more complex this current implementation is not realistic or easy to maintain.
The text was updated successfully, but these errors were encountered: