-
Notifications
You must be signed in to change notification settings - Fork 3.7k
ipsec: phase out bpf_network #33704
Copy link
Copy link
Closed
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/encryptionImpacts encryption support such as IPSec, WireGuard, or kTLS.Impacts encryption support such as IPSec, WireGuard, or kTLS.feature/ipsecRelates to Cilium's IPsec featureRelates to Cilium's IPsec featurekind/tech-debtTechnical debtTechnical debtpinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.
Description
Background:
IPsec has been using its own BPF program (bpf_network) on the Ingress of native network interfaces, to handle inbound IPsec traffic. This gets configured via --encrypt-interface.
But as the support for IPsec in the "normal" from-netdev program is stabilizing, we eventually want to remove the bpf_network program.
Proposal:
Deprecate the --encrypt-interface option, and fully replace the usage of bpf_network with bpf_host.
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/encryptionImpacts encryption support such as IPSec, WireGuard, or kTLS.Impacts encryption support such as IPSec, WireGuard, or kTLS.feature/ipsecRelates to Cilium's IPsec featureRelates to Cilium's IPsec featurekind/tech-debtTechnical debtTechnical debtpinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.