bpfman / bpfman/bpfman-operator

Investigate CSI Behavior

Open
#91 1 comment 0 reactions 2 assignees Claimed by @Billy99 View on GitHub
Dominant language
Go
Stars
38
Forks
27
PR merge metrics
No merged PRs in 30d

Description

Currently, an application using bpfman must identify the maps it requires upfront in its deployment.yaml file. Then, the application doesn't load until all maps are available for mounting, which implies that all of the eBPF programs needed to create the maps must be loaded before the application can be loaded.

Is it possible to decouple the loading of the application from the loading of the eBPF programs so that it will load even if the maps haven't been created yet?

A use case for this behavior is an application for which eBPF programs are dynamically loaded and unloaded based on configuration or other events.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.