[CORE-11600] Streamline BPF installation #4058
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Context
To drive adoption of Calico’s BPF dataplane, we aim to simplify its setup by automating current manual steps. The goal is to support default BPF installations on clusters that iinitially use kube-proxy (e.g., via kubeadm) without requiring user configuration.
This PR extends the mount-bpffs init container to handle the initial BPF setup required for network communication when BPF is enabled and kube-proxy is disabled.
Changes
The default behavior remains unchanged. If the user does not opt in via
BPFBootstrapMode
, the Operator will behave exactly as it does currently.Error Handling
If the user opts in but any requirements are not met, the Operator will report a degraded status via TigeraStatus.
Tests
Implemented UTs in the Core Controller.
FVs and EEs are likely not necessary for this change.
Release Note
For PR author
make gen-files
make gen-versions
For PR reviewers
A note for code reviewers - all pull requests must have the following:
kind/bug
if this is a bugfix.kind/enhancement
if this is a a new feature.enterprise
if this PR applies to Calico Enterprise only.