Repository navigation
[Architecture]: Introducing eBPF #82
Description
Is your feature request related to a problem?
- Yes
Problem Description
Sidecar proxies introduce significant overhead by adding extra complexity to the networking layer. If service A wants to communicate with service B, the message must pass through two sidecar proxies, like in the example below:
A --> Proxy A --> Proxy B --> B
Solution
By leveraging eBPF (Extended Berkeley Packet Filter), we can implement the networking layer directly at the kernel level, bypassing the user space and reducing the overhead introduced by sidecar proxies.
Additional Info
Demonstration of the communication:
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[#82]: added a simple xdp program (building test)
[#82]: added small building script
[#82]: added services bpf map
[#82]: Added str_to_u8_64 function to convert &str types to &[u8;64]
[#82]: added cache service in "service discovery" using a bpf map sha…
[#82]: updated xdp main.rs (comments)
[#82]: attached xdp program to interface
[#82]: added bpf map module
8 remaining items
[#82]: changed comments filter.rs
[#82]: adapted loadbalancer structure for use in kubernetes environment
[#82]: added loadbalancer dockerfile. added build script
[#82]: added loadbalancer kubernetes manifest file. modified deploy-t…
[#82]: updated map,rs comments
[#82]: updated comments in filter.rs