You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 6, 2026. It is now read-only.
Since some network plugings like Cilium attach eBPF programts to all interfaces, once a workload claims and interface it may want to get total ownership, so they should be able to express the intent to get the interface in a clean state without the existing eBPF programs. However, there maybe other eBPF programs that people may want to keep (we need to validate this), as some security or monitoring.
Implementation wise it should not be much difficult, we already have logic that allow to get the existing programs attached to both the TC and TCX hooks
Since some network plugings like Cilium attach eBPF programts to all interfaces, once a workload claims and interface it may want to get total ownership, so they should be able to express the intent to get the interface in a clean state without the existing eBPF programs. However, there maybe other eBPF programs that people may want to keep (we need to validate this), as some security or monitoring.
Implementation wise it should not be much difficult, we already have logic that allow to get the existing programs attached to both the TC and TCX hooks
dranet/pkg/inventory/net.go
Lines 74 to 119 in 5b1390b
So it is just deciding on the API
dranet/pkg/apis/types.go
Lines 35 to 65 in 5b1390b
and then on the corresponding hook, to detach the programs