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

Is there an overhead introduced by the Amazon VPC CNI plugin for EKS on the MTU (Maximum Transmission Unit) #3085

Closed
gsustek opened this issue Oct 23, 2024 · 3 comments

Comments

@gsustek
Copy link

gsustek commented Oct 23, 2024

If i set :
AWS_VPC_ENI_MTU = 1500

how much i need to set
POD_MTU = ?

Does this calculation applies?
Effective MTU = Default MTU - VXLAN Overhead

Sorry for question,
is even an AWS VPC CNI is an overlay network?

@orsenthil
Copy link
Member

Is AWS VPC CNI is an overlay network?

No, it is not an overlay network plugin.

@orsenthil
Copy link
Member

As answered, AWS VPC CNI is not an overlay plugin. VXLAN and VXLAN Overhead doesn't come into picture.

The POD_MTU was supported when customers tried to use Cilium with Wireguard as chain plugin with VPC CNI (before VPC CNI supported Network Policy). When customers ran into this and requested for the ability set MTU at pod level (because cilium wireguard extension was using overlay and providing Network Policy), it was introduced as support here - #2606

If you are only using VPC CNI, you don't need set POD_MTU and it will default to AWS_VPC_ENI_MTU.

Hope this clarifies.

Copy link

github-actions bot commented Nov 5, 2024

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants