Cache BPF objects once on amd64 and reuse for multi-arch builds#12365
Draft
hjiawei wants to merge 1 commit intoprojectcalico:masterfrom
Draft
Cache BPF objects once on amd64 and reuse for multi-arch builds#12365hjiawei wants to merge 1 commit intoprojectcalico:masterfrom
hjiawei wants to merge 1 commit intoprojectcalico:masterfrom
Conversation
BPF bytecode targets the BPF virtual machine, not the host CPU, making compiled .o files architecture-independent across amd64, arm64, and ppc64le. This change builds BPF objects once on amd64 and caches them via Semaphore cache for reuse by multi-arch and push-images builds. The PRE_BUILT_BPF_OBJECTS Makefile flag skips BPF .o compilation while still building the architecture-specific libbpf (needed for CGO linking). Both Felix and Node Build jobs store the cache so multi-arch jobs always have BPF objects available regardless of which build blocks run. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
BPF bytecode targets the BPF virtual machine, not the host CPU, making compiled .o files architecture-independent across amd64, arm64, and ppc64le. This change builds BPF objects once on amd64 and caches them via Semaphore cache for reuse by multi-arch and push-images builds.
The PRE_BUILT_BPF_OBJECTS Makefile flag skips BPF .o compilation while still building the architecture-specific libbpf (needed for CGO linking). Both Felix and Node Build jobs store the cache so multi-arch jobs always have BPF objects available regardless of which build blocks run.
Release note: