Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate CSI Behavior #91

Open
anfredette opened this issue Aug 5, 2024 · 0 comments
Open

Investigate CSI Behavior #91

anfredette opened this issue Aug 5, 2024 · 0 comments
Assignees
Milestone

Comments

@anfredette
Copy link
Contributor

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.

@github-project-automation github-project-automation bot moved this to 🆕 New in bpfman Aug 5, 2024
@anfredette anfredette added this to the Q3-2024 milestone Aug 8, 2024
@anfredette anfredette modified the milestones: Q3-2024, Q4-2024 Oct 24, 2024
msherif1234 pushed a commit to msherif1234/bpfman-operator that referenced this issue Nov 15, 2024
…/ocp-bpfman-operator-bundle

chore(deps): update ocp-bpfman-operator-bundle to 331bb52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants