From 3be90bf42204a3f8b97c58e29be68bc081cdd565 Mon Sep 17 00:00:00 2001 From: adityasamant25 Date: Tue, 2 Apr 2024 19:40:07 +0530 Subject: [PATCH] Remove the reference to installed-state CR (#14816) --- .../en/docs/setup/install/istioctl/index.md | 22 ------------------- 1 file changed, 22 deletions(-) diff --git a/content/en/docs/setup/install/istioctl/index.md b/content/en/docs/setup/install/istioctl/index.md index c86c0b8909..c1cbc0ec9a 100644 --- a/content/en/docs/setup/install/istioctl/index.md +++ b/content/en/docs/setup/install/istioctl/index.md @@ -106,28 +106,6 @@ to install the `demo` profile: $ istioctl install --set profile=demo {{< /text >}} -## 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`. -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-egressgateway 1/1 1 1 25s -istio-ingressgateway 1/1 1 1 24s -istiod 1/1 1 1 20s -{{< /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. - ## Display the list of available profiles You can display the names of Istio configuration profiles that are