-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Support fragment tracking for BPF DSR / SNAT with kube-proxy replacement #11180
Copy link
Copy link
Open
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.area/loadbalancingImpacts load-balancing and Kubernetes service implementationsImpacts load-balancing and Kubernetes service implementationsfeature/snatRelates to SNAT or Masquerading of trafficRelates to SNAT or Masquerading of traffickind/featureThis introduces new functionality.This introduces new functionality.pinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.
Description
Metadata
Metadata
Assignees
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.area/loadbalancingImpacts load-balancing and Kubernetes service implementationsImpacts load-balancing and Kubernetes service implementationsfeature/snatRelates to SNAT or Masquerading of trafficRelates to SNAT or Masquerading of traffickind/featureThis introduces new functionality.This introduces new functionality.pinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.
Follow-up to #10264: Support fragment tracking with BPF-based DSR and SNAT.
Pretty sure
l4_modify_port()andl4_load_port()in bpf/lib/l4.h, on SNAT path, should be changed to get fragment support. DSR probably needs other changes too.The relevant metrics and tests need also be added.