Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix istiooperator upgrade guide #16262

Merged
merged 3 commits into from
Feb 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,11 @@ Users who prefer the operator pattern for running Istio can migrate to either of

### Migrating to Helm

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.
Helm migration requires translating your `IstioOperator` YAML into Helm values. Istio 1.24 and above includes a `manifest translate` command to perform this operation. The output is a `values.yaml` file, and a shell script to install equivalent Helm charts.

{{< text bash >}}
$ istioctl manifest translate -f istio.yaml
{{< /text >}}

### Migrating to istioctl

Expand All @@ -43,7 +47,7 @@ $ kubectl get IstioOperator
Using the name of your resource, download your operator configuration in YAML format:

{{< text bash >}}
$ kubectl get IstioOperator <name> > istio.yaml
$ kubectl get IstioOperator <name> -o yaml > istio.yaml
{{< /text >}}

Disable the In-Cluster Operator. This will not disable your control plane or disrupt your current mesh traffic.
Expand Down