Adjust MTU only for pods using the egress gateway or SRv6 encapsulations #22295
Labels
feature/egress-gateway
Impacts the egress IP gateway feature.
feature/srv6
Impacts the SRv6 feature.
kind/feature
This introduces new functionality.
pinned
These issues are not marked stale by our issue bot.
sig/datapath
Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
Today, whenever egress gateway is used, we set the MTU of pods to account for the additional overhead of the tunnel (to the gateway node) regardless of whether the pods in question are actually going to use the egress gateway. We are planning to do the same for SRv6 (cf. #22294).
We however know, for both of those features, when pods are going to use encapsulation. This information is given by the podSelector in the CRD used for configuration. We should thus be able to dynamically configure the MTU according to whether encapsulation is going to be used.
The text was updated successfully, but these errors were encountered: