You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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?
The text was updated successfully, but these errors were encountered: