Skip to content

Commit 5cef367

Browse files
committed
nit
Signed-off-by: Benjamin Kilimnik <bkilimnik@pixielabs.ai>
1 parent efd6b97 commit 5cef367

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/04-tutorials/04-custom-data/01-distributed-bpftrace-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ The `TraceProgram` object currently accepts the following parameters:
180180
- `max_kernel`: The maximum kernel version on which the program should be deployed.
181181
- `min_kernel`: The minimum kernel version on which the program should be deployed.
182182

183-
You can use the `TraceProgram` object to deploy different BPFtrace programs based on the kernel version of the nodes in your cluster. For example, you might have one version of a BPFtrace program that works on kernel versions up to 5.18, and another version that works on kernel versions 5.19 and above. You can define two `TraceProgram` objects and use them both in the `UpsertTracepoint` function.
183+
You can use the `TraceProgram` object to deploy different BPFtrace programs based on the kernel version of the nodes in your cluster. For example, you might have one version of a BPFtrace program that works on kernel versions up to 5.18, and another version that works on kernel versions 5.19 and above. $0 and $1 are placeholders for BPFtrace programs. You can define two `TraceProgram` objects and use them both in the `UpsertTracepoint` function.
184184

185185
Here's an example:
186186

0 commit comments

Comments
 (0)