@@ -8,25 +8,60 @@ of [bpftrace](https://github.com/iovisor/bpftrace) programs in your Kubernetes c
8
8
<!-- toc -->
9
9
10
10
- [ Installing] ( #installing )
11
- * [ Source] ( #source )
12
- * [ Packages] ( #packages )
13
- + [ Arch - AUR] ( #arch---aur )
11
+ - [ Pre-built binaries] ( #pre-built-binaries )
12
+ - [ Source] ( #source )
13
+ - [ Packages] ( #packages )
14
+ - [ Arch - AUR] ( #arch---aur )
14
15
- [ Architecture] ( #architecture )
15
16
- [ Usage] ( #usage )
16
- * [ Run a program from string literal] ( #run-a-program-from-string-literal )
17
- * [ Run a program from file] ( #run-a-program-from-file )
18
- * [ Run a program against a Pod] ( #run-a-program-against-a-pod )
19
- * [ Running against a Pod vs against a Node] ( #running-against-a-pod-vs-against-a-node )
20
- * [ Using a custom service account] ( #using-a-custom-service-account )
21
- * [ Executing in a cluster using Pod Security Policies] ( #executing-in-a-cluster-using-pod-security-policies )
22
- * [ More bpftrace programs] ( #more-bpftrace-programs )
17
+ - [ Run a program from string literal] ( #run-a-program-from-string-literal )
18
+ - [ Run a program from file] ( #run-a-program-from-file )
19
+ - [ Run a program against a Pod] ( #run-a-program-against-a-pod )
20
+ - [ Running against a Pod vs against a Node] ( #running-against-a-pod-vs-against-a-node )
21
+ - [ Using a custom service account] ( #using-a-custom-service-account )
22
+ - [ Executing in a cluster using Pod Security Policies] ( #executing-in-a-cluster-using-pod-security-policies )
23
+ - [ More bpftrace programs] ( #more-bpftrace-programs )
23
24
- [ Status of the project] ( #status-of-the-project )
24
25
- [ Contributing] ( #contributing )
25
26
26
27
<!-- tocstop -->
27
28
28
29
## Installing
29
30
31
+ ### Pre-built binaries
32
+
33
+ See the [ release] ( https://github.com/iovisor/kubectl-trace/releases ) page for the full list of pre-built assets.
34
+
35
+ The commands here show ` amd64 ` versions, ` 386 ` versions are available in the releases page.
36
+
37
+ ** Linux**
38
+
39
+ ``` bash
40
+ curl -Lo https://github.com/iovisor/kubectl-trace/releases/download/v0.1.0-rc.0/kubectl-trace_0.1.0-rc.0_linux_amd64.tar.gz
41
+ tar -xvf kubectl-trace.tar.gz
42
+ mv kubectl-trace /usr/local/bin/kubectl-trace
43
+ ```
44
+
45
+ ** OSX**
46
+
47
+ ``` bash
48
+ curl -Lo https://github.com/iovisor/kubectl-trace/releases/download/v0.1.0-rc.0/kubectl-trace_0.1.0-rc.0_linux_amd64.tar.gz
49
+ tar -xvf kubectl-trace.tar.gz
50
+ mv kubectl-trace /usr/local/bin/kubectl-trace
51
+ ```
52
+
53
+
54
+ ** Windows**
55
+
56
+ In PowerShell v5+
57
+ ``` powershell
58
+ $url = "https://github.com/iovisor/kubectl-trace/releases/download/v0.1.0-rc.0/kubectl-trace_0.1.0-rc.0_windows_amd64.zip"
59
+ $output = "$PSScriptRoot\kubectl-trace.zip"
60
+
61
+ Invoke-WebRequest -Uri $url -OutFile $output
62
+ Expand-Archive "$PSScriptRoot\kubectl-trace.zip" -DestinationPath "$PSScriptRoot\kubectl-trace"
63
+ ```
64
+
30
65
### Source
31
66
32
67
```
@@ -52,13 +87,7 @@ yay -S kubectl-trace-git
52
87
53
88
## Architecture
54
89
55
- Since it is a kubectl plugin, kubectl-trace doesn't require you to install any component directly
56
- to your kubernetes cluster in order to execute your bpftrace programs, however when you point it to
57
- a cluster, it will schedule a temporary job there called ` trace-runner ` that executes the program.
58
-
59
- This figure, shows the general idea:
60
-
61
- ![ Kubectl trace architecture diagram] ( docs/img/kubectl-trace-architecture.png )
90
+ See [ architecture.md] ( /docs/architecture.md )
62
91
63
92
## Usage
64
93
0 commit comments