Conversation
|
Coverage increased (+1.0%) to 45.543% when pulling dfcff21b84e2127af444638aec431a3720f2a839 on pr/tklauser/remove-go-bindata into 8fc4bde on master. |
1af404d to
c604dbe
Compare
|
test-me-please |
c604dbe to
922355e
Compare
|
test-me-please |
|
test-docs-please |
|
test-me-please |
|
test-me-please |
|
CI failed due to well known flakes: |
|
test-me-please |
Do you think we should add a more specific error message, e.g. instructing the user to run
What do you mean by standalone? Just running on a host without k8s/docker/etc.? |
Yep, something along the lines:
Running cilium-agent directly on a host, i.e. not in a constainer (e.g. |
922355e to
3cfeed5
Compare
|
@brb The following message is now logged if the BPF template directory does not exist: |
|
test-me-please |
Use of go-bindata dates back from times when people ran Cilium as static
binary. This has become uncommon and users either use the container
image or a package manager which will both ship /var/lib/cilium directly
so there is no need to unpack any assets via the binary.
For people still wanting to use Cilium as a static binary, e.g. for
local development provide the
install-bpfMakefile target to installthe BPF assets into
/var/lib/cilium.This saves ~380 kB in the resulting cilium-agent binary:
Updates #10056
Fixes #10075
This change is