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

Add helm upgrade warning (#3744)

This commit is contained in:
Frank Budinsky 2019-03-18 16:28:39 -04:00 committed by istio-bot
parent d87d9b0fde
commit 7fc10c7590
2 changed files with 21 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/docs/setup/kubernetes/upgrade/notice/index.md
View File

@ -11,7 +11,7 @@ For an overview of new features introduced with Istio 1.1, please refer to the [
## Installation
- Istio’s CRDs have been placed into their own Helm chart `istio-init`. This prevents loss of custom resource data, facilitates the upgrade process, and enables Istio to evolve beyond a Helm-based installation. The [upgrade documentation](/docs/setup/kubernetes/upgrade/) provides the proper procedures for upgrading from Istio 1.0.6 to Istio 1.1. Please follow these instructions carefully when upgrading. If `certmanager` is desired, use the `--set certmanager=true` flag when installing both `istio-init` and Istio charts with either `template` or `tiller` installation modes.
- Istio’s CRDs have been placed into their own Helm chart `istio-init`. This prevents loss of custom resource data, facilitates the upgrade process, and enables Istio to evolve beyond a Helm-based installation. The [upgrade documentation](/docs/setup/kubernetes/upgrade/steps/) provides the proper procedures for upgrading from Istio 1.0.6 to Istio 1.1. Please follow these instructions carefully when upgrading. If `certmanager` is desired, use the `--set certmanager=true` flag when installing both `istio-init` and Istio charts with either `template` or `tiller` installation modes.
- The 1.0 `istio-remote` chart used for [multicluster VPN](/docs/setup/kubernetes/install/multicluster/vpn/) and [multicluster split horizon](/docs/examples/multicluster/split-horizon-eds/) remote cluster installation has been consolidated into the Istio chart. To generate an equivalent `istio-remote` chart, use the `--set global.istioRemote=true` flag.
- Addons are no longer exposed via separate load balancers. Instead addons are now exposed via the Ingress Gateway. To expose an addon via the Ingress Gateway, please follow the [Remotely Accessing Telemetry Addons](/docs/tasks/telemetry/gateways/) guide.
- The built-in Istio Statsd collector has been removed. Istio retains the capability of integrating with your own Statsd collector.

20
content/docs/setup/kubernetes/upgrade/steps/index.md
View File

@ -27,6 +27,26 @@ and change directory to the new release directory.
### Control plane upgrade
{{< warning >}}
Helm has significant problems when upgrading CRDs.
We believe we have solved these with the introduction of the `istio-init` chart.
However, because of the wide variety of Helm and Tiller versions used with previous Istio deployments,
ranging from 2.7.2 to 2.12.2, we recommend an abundance of caution by
backing up your custom resource data, before proceeding with the upgrade:
{{< text bash >}}
$ kubectl get crds | grep istio.io | cut -f1-1 -d "." | \
xargs -n1 -i sh -c "kubectl get --all-namespaces -oyaml {}; echo ---" > $HOME/ISTIO_RESTORE_DATA.yaml
{{< /text >}}
Restore if necessary:
{{< text bash >}}
$ kubectl apply -f $HOME/ISTIO_RESTORE_DATA.yaml
{{< /text >}}
{{< /warning >}}
The Istio control plane components include: Citadel, Ingress gateway, Egress gateway, Pilot, Galley, Policy, Telemetry and
Sidecar injector. Choose one of the following two **mutually exclusive** options to update the control plane: