-
Notifications
You must be signed in to change notification settings - Fork 166
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: update installation instructions
Signed-off-by: Lorenzo Fontana <lo@linux.com>
- Loading branch information
Showing
2 changed files
with
55 additions
and
17 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
# Architecture | ||
|
||
Since it is a kubectl plugin, kubectl-trace doesn't require you to install any component directly | ||
to your kubernetes cluster in order to execute your bpftrace programs, however when you point it to | ||
a cluster, it will schedule a temporary job there called `trace-runner` that executes the program. | ||
|
||
This figure, shows the general idea: | ||
|
||
![Kubectl trace architecture diagram](/docs/img/kubectl-trace-architecture.png) |