istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add istioctl bug-report command for reporting bugs (#8573) 

* Add istioctl bug-report command for reporting bugs

* add tip

Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>

Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
This commit is contained in:
Shamsher Ansari 2020-11-25 23:59:34 +05:30 committed by GitHub
parent f1be3d55d4
commit 29626e8185
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
content/en/about/bugs/index.md
View File

@ -26,24 +26,20 @@ to learn what to do.
If you're running on Kubernetes, consider including a cluster state
archive with your bug report.
For convenience, you can run a dump script to produce an archive containing
For convenience, you can run the `istioctl bug-report` command to produce an archive containing
all of the relevant state from your Kubernetes cluster:
* Run via `curl`:
{{< text bash >}}
$ curl {{< github_file >}}/tools/dump_kubernetes.sh | sh -s -- -z
$ istioctl bug-report
{{< /text >}}
* Run locally, from the release directory's root:
Then attach the produced `bug-report.tgz` with your reported problem.
{{< text bash >}}
$ @tools/dump_kubernetes.sh@ -z
{{< /text >}}
{{< tip >}}
The `istioctl bug-report` command is only available with `istioctl` version `1.8.0` and higher but it can be used to also collect the information from an older Istio version installed in your cluster.
{{< /tip >}}
Then attach the produced `istio-dump.tar.gz` with your reported problem.
If you are unable to use the dump script, please attach your own archive
If you are unable to use the `bug-report` command, please attach your own archive
containing:
* Pods, services, deployments, and endpoints across all namespaces: