From fc812ed0451696b7b4bafbafbadcf19c370883ba Mon Sep 17 00:00:00 2001 From: David Calvert Date: Fri, 21 Feb 2025 21:32:28 +0100 Subject: [PATCH] docs: fix istiooperator upgrade guide Signed-off-by: David Calvert --- .../in-cluster-operator-deprecation-announcement/index.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/en/blog/2024/in-cluster-operator-deprecation-announcement/index.md b/content/en/blog/2024/in-cluster-operator-deprecation-announcement/index.md index 2292cbb8b9a8..3db40154878c 100644 --- a/content/en/blog/2024/in-cluster-operator-deprecation-announcement/index.md +++ b/content/en/blog/2024/in-cluster-operator-deprecation-announcement/index.md @@ -32,6 +32,12 @@ Users who prefer the operator pattern for running Istio can migrate to either of Helm migration requires translating your `IstioOperator` YAML into a Helm `values.yaml` file. Tooling to support this migration will be provided alongside the Istio 1.24 release. +Translate an IstioOperator YAML file into helm values: + +{{< text bash >}} +istioctl manifest translate -f istio.yaml +{{< /text >}} + ### Migrating to istioctl Identify your `IstioOperator` custom resource: there should be only one result. @@ -43,7 +49,7 @@ $ kubectl get IstioOperator Using the name of your resource, download your operator configuration in YAML format: {{< text bash >}} -$ kubectl get IstioOperator > istio.yaml +$ kubectl get IstioOperator -o yaml > istio.yaml {{< /text >}} Disable the In-Cluster Operator. This will not disable your control plane or disrupt your current mesh traffic.