Better error reporting for BPF dataplane #69
Labels
area/dataplane
area/maintenance
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Today for all our TC BPF programs we execute our programs but ALWAYS return
TC_ACT_OK
regardless of the success or failure within our BPF program.for example
We should rethink this and at the very least let the user know that our programs failed in the event of a problem. I think a log would be fine for now.
The text was updated successfully, but these errors were encountered: