Changes/DefaultBpfman

Fedora 40: Bpfman as default eBPF manager (Self-Contained Change proposal)

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Owner

• Name: Daniel Mellado
• Email: dmellado@fedoraproject.org
• Name: Dave Tucker
• Email: datucker@redhat.com
• Name: Toke Høiland-Jørgensen
• Email: thoiland@redhat.com

Current status

• Targeted release: Fedora Linux 40
• Last updated: 2024-01-10
• [<will be assigned by the Wrangler> devel thread]
• FESCo issue: <will be assigned by the Wrangler>
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

bpfman operates as an eBPF manager, focusing on simplifying the deployment and administration of eBPF programs. Its notable features encompass:

• System Overview: Provides insights into how eBPF is utilized in your system.
• eBPF Program Loader: Includes a built-in program loader that supports program cooperation for XDP and TC programs, as well as

 deployment of eBPF programs from OCI images.

• eBPF Filesystem Management: Manages the eBPF filesystem, facilitating the deployment of eBPF applications without requiring

 additional privileges.

Our program loader and eBPF filesystem manager ensure the secure deployment of eBPF applications. Furthermore, bpfman includes a Kubernetes operator, extending these capabilities to Kubernetes. This allows users to confidently deploy eBPF through custom resource definitions across nodes in a cluster.

Scope

• Proposal owners:

• Other developers:

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with Community Initiatives:

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)