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

Show examples in `Check what's installed` section (#7903) 

* Show examples in `Check what's installed` section

* Update wording

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

* emove snippet

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

* Update content/en/docs/setup/install/istioctl/index.md

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

Co-authored-by: Frank Budinsky <frankb@ca.ibm.com>
This commit is contained in:
Jonh Wendell 2020-08-11 12:01:37 -04:00 committed by GitHub
parent 4801cd62fa
commit 8b4752cf8e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/en/docs/setup/install/istioctl/index.md
View File

@ -94,7 +94,21 @@ $ istioctl install --set profile=demo
## Check what's installed
The `istioctl` command saves the `IstioOperator` CR that was used to install Istio in a copy of the CR named `installed-state`.
You can inspect this CR if you lose track of what is installed in a cluster.
Instead of inspecting the deployments, pods, services and other resources that were installed by Istio, for example:
{{< text bash >}}
$ kubectl -n istio-system get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
istio-ingressgateway 1/1 1 1 49m
istiod 1/1 1 1 49m
{{< /text >}}
You can inspect the `installed-state` CR, to see what is installed in the cluster, as well as all custom settings.
For example, dump its content into a YAML file using the following command:
{{< text bash >}}
$ kubectl -n istio-system get IstioOperator installed-state -o yaml > installed-state.yaml
{{< /text >}}
The `installed-state` CR is also used to perform checks in some `istioctl` commands and should therefore not be removed.