[EBPF] Allow --compile-only and cross-compile in kmt.build

[gjulianm]

What does this PR do?

Enables cross-compilation in the kmt.build task. Also adds an argument to build the binary without copying it to remote VMs.

Motivation

Enable testing `system-probe´ in different architectures.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

[agent-platform-auto-pr]

[Fast Unit Tests Report]

On pipeline 37667963 (CI Visibility). The following jobs did not run any unit tests:

Jobs:

• tests_deb-arm64-py3
• tests_deb-x64-py3
• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_rpm-arm64-py3
• tests_rpm-x64-py3
• tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: a2259e48-9a32-49f0-b910-8d1b21ecd691 Metrics dashboard Target profiles

Baseline: 9551500
Comparison: 6d85826

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

No significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	tcp_syslog_to_blackhole	ingress throughput	+3.75	[-9.52, +17.02]	Logs
➖	otel_to_otel_logs	ingress throughput	+0.41	[-0.40, +1.22]	Logs
➖	idle	memory utilization	+0.24	[+0.20, +0.27]	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	Logs
➖	file_tree	memory utilization	-0.08	[-0.12, -0.03]	Logs
➖	pycheck_1000_100byte_tags	% cpu utilization	-0.21	[-5.03, +4.62]	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.60	[-1.50, +0.29]	Logs
➖	basic_py_check	% cpu utilization	-0.67	[-3.42, +2.08]	Logs

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

[val06]

approved with suggestion

[val06]

consider (if not too much work) extracting the remaining of this function to another function and call it only if compile_only == False

[brycekahle]

Also adds an argument to build the binary without copying it to remote VMs.

What is the use case of this?

[gjulianm]

Also adds an argument to build the binary without copying it to remote VMs.

What is the use case of this?

Mostly for testing and development of KMT, and parity with kmt.prepare which has a --compile-only flag too.

[gjulianm]

/merge

[dd-devflow]

🚂 MergeQueue: pull request added to the queue

The median merge time in main is 25m.

Use /merge -c to cancel this operation!