You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2ec917f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: cli/docs/kubectl-shovel_dump.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,7 @@ Also use `-n`/`--namespace` if your pod is not in current context's namespace:
56
56
-p, --process-id int The process ID to collect the trace from (default 1)
57
57
--request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
58
58
-s, --server string The address and port of the Kubernetes API server
59
+
-t, --store-output-on-host Flag, indicating that output should be stored on host /tmp folder
59
60
--tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
60
61
--token string Bearer token for authentication to the API server
61
62
--type type The kinds of information that are collected from process. Supported types:
Copy file name to clipboardExpand all lines: cli/docs/kubectl-shovel_gcdump.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Get dotnet-gcdump results
4
4
5
5
### Synopsis
6
6
7
-
This subcommand will run dotnet-gcdump tool for running in k8s appplication.
7
+
This subcommand will run dotnet-gcdump tool for running in k8s application.
8
8
Result will be saved locally so you'll be able to analyze it with appropriate tools.
9
9
You can find more info about dotnet-gcdump tool by the following links:
10
10
@@ -54,6 +54,7 @@ Also use `-n`/`--namespace` if your pod is not in current context's namespace:
54
54
-p, --process-id int The process ID to collect the trace from (default 1)
55
55
--request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
56
56
-s, --server string The address and port of the Kubernetes API server
57
+
-t, --store-output-on-host Flag, indicating that output should be stored on host /tmp folder
57
58
--timeout timeout Give up on collecting the GC dump if it takes longer than this many seconds.
58
59
Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".
59
60
Will be rounded to seconds. If no unit provided defaults to seconds.
--request-timeout string The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
94
94
-s, --server string The address and port of the Kubernetes API server
95
+
-t, --store-output-on-host Flag, indicating that output should be stored on host /tmp folder
95
96
--tls-server-name string Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
96
97
--token string Bearer token for authentication to the API server
97
98
--user string The name of the kubeconfig user to use
0 commit comments