Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RFC: Rename bpf host routing options from "legacy / bpf" to "on / off" #32131

Open
joestringer opened this issue Apr 22, 2024 · 0 comments
Open

RFC: Rename bpf host routing options from "legacy / bpf" to "on / off" #32131

joestringer opened this issue Apr 22, 2024 · 0 comments
Labels
kind/enhancement This would improve or streamline existing functionality. sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages.

Comments

@joestringer
Copy link
Member

Feedback from @brb here:

IMO the BPF host routing is still an experimental feature (e.g., in the ENI mode it's discouraged). For me "legacy" reads as if something is bad / not wanted. Maybe we could improve the wording by just saying BPF routing: (on | off).

cc @cilium/sig-datapath @borkmann
@joestringer joestringer added kind/enhancement This would improve or streamline existing functionality. sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. labels Apr 22, 2024
@joestringer joestringer mentioned this issue Apr 22, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement This would improve or streamline existing functionality. sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joestringer