Skip to content

Releases: astoycos/bpfman

v0.4.2

21 Jun 17:47
Compare
Choose a tag to compare

The v0.4.2 release is a patch release which is mainly cut pull in some OLM bundle
fixes for the bpfman-operator OLM manifest deployment.

What's Changed

New Contributors

Full Changelog: bpfman/bpfman@v0.4.1...v0.4.2

v0.4.1

03 May 19:44
Compare
Choose a tag to compare

The v0.4.1 release is a patch release which includes some bug fixes found
in the original v0.4.0 release. Additionally support has been added for deploying
the example applications as unprivileged containers on productions systems which
enable SELinux by default.

Users can now access released RPMs from the bpfman COPR repo and nightly RPMs from the bpfman-next COPR repo.

For even more details Please see the individual commit
messages shown below.

What's Changed

New Contributors

Full Changelog: bpfman/bpfman@v0.4.0...v0.4.1

v0.4.0

10 Apr 15:33
Compare
Choose a tag to compare

The v0.4.0 release is a minor release and the first following the project
rename from bpfd to bpfman.
From a design perspective, this release fully transitions bpfman to be a
library rather than a daemon. From a user's perspective the main
difference is that the bpfctl CLI can now simply be called directly with the
bpfman binary, otherwise all of the major commands remain the same.

On top of transitioning to a library the community has also implemented some
exciting new features:

  • Support for Uprobe Programs
  • The ability to attach Uprobes inside containers (locally and in Kubernetes), see the blog for more.
  • Support for Kprobe Programs
  • Support for Fentry Programs
  • Support for Fexit Programs

Additionally this release provides some new binary crates. The bpfman-rpc binary
allows other languages to call into the bpfman library using the existing
grpc api defined in the bpfman-api crate bindings. The bpf-metrics-exporter,
and the bpf-log-exporterbinaries allow users to gather useful information regarding
the bpf subsystem.

Warning

FEATURE DEPRECATION: The ability to view all programs on a given node via the
BpfProgram CRD has been deprecated. Instead the community now provides
the bpf-metrics-exporter crate.

Warning

The CSI feature still requires a privileged application on distributions which
enable SELinux by default (i.e Red Hat Openshift). Therefore we've shipped a set of
deployment configs specifically for openshift in this release, see the additional
go-<example>-counter-install-ocp.yaml artifacts included in the release
payload. Stay tuned to #829 for
updates.

What's Changed (excluding dependency bumps)

Read more

v0.3.0

16 Oct 04:15
9f7355e
Compare
Choose a tag to compare

The v0.3.0 release is our second official minor release of the the bpfd project.

WARNING
This release contains breaking changes for both the core bpfd GRPC API
as well as the Kubernetes CRDs. There is no backwards compatibility or guarantees
with any of our previous releases at this point.

The following describes some of the major new features/updates:

  • The ability to list and get kernel information for ALL programs regardless
    of whether they were loaded by bpfd or another process

  • Deprecation of bpfd specific UUIDs for each loaded program in favor of the
    standard generated kernel ID for all programs regardless of what process loaded them.

  • Support for some new bpf program types:

    • Uprobe
    • Uretprobe
    • Kprobe
    • KretProbe
      Along with their corresponding K8s API CRD Resources (Uprobe and Kprobe CRDs)
  • bpfctl got some exciting new features + functionality:

    • The ability to pre-pull a bytecode image from a remote repository for later use
    • The ability to get a program based on Kernel ID
    • The ability to load a program with user determined metadata labels which the user
      can later use to filter via a bpfctl list
    • Much better formatting and both kernel + bpfd information feedback on load, list
      and get calls
  • For maps, multiple programs can now share the same maps via the map_owner_id field
    allowing for data sharing across various programs which are loaded via bpfd

  • Removal of the cert-manager dependency in the bpfd kubernetes deployment

  • Preliminary CSI(Container Storage Interface) support which allows applications
    to receive their maps in kubernetes applications with a simple custom volume type

New Contributors

Full Changelog: bpfman/bpfman@v0.2.1...v0.3.0