-
Notifications
You must be signed in to change notification settings - Fork 3.7k
bpf_lxc: support LB for nodeports in the per-packet LB (wildcard lookup) #34777
Copy link
Copy link
Closed
Closed
Copy link
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 implementationskind/enhancementThis would improve or streamline existing functionality.This would improve or streamline existing functionality.pinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.
Milestone
Description
Background:
When not using the SocketLB, in-cluster access to a remote node's nodeports is not handled by the per-packet LB in from-container. Instead it gets processed at the remote node's from-netdev program (the "N/S path").
This is different from the SocketLB, where Cilium supports wildcard lookups that match the nodeport and match the IP against node identities (either local or remote).
Proposal:
Let's harmonize the behaviour by consistently LBing such in-cluster access to nodeports at the source.
Reactions are currently unavailable
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 implementationskind/enhancementThis would improve or streamline existing functionality.This would improve or streamline existing functionality.pinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.