mirror of https://github.com/istio/istio.io.git
remove helm upgrade (#6725)
* remove helm upgrade * no need to use table now * address eric's comment
This commit is contained in:
Istio Automation
GitHub
parent
812c91672a
commit
0add45e7d0
|
|
@ -33,14 +33,7 @@ and change directory to the new release directory.
|
|||
### Istio CNI upgrade
|
||||
|
||||
If you have installed or are planning to install [Istio CNI](/docs/setup/additional-setup/cni/),
|
||||
choose one of the following **mutually exclusive** options to check whether
|
||||
Istio CNI is already installed and to upgrade it:
|
||||
|
||||
{{< tabset category-name="controlplaneupdate" >}}
|
||||
{{< tab name="Kubernetes rolling update" category-value="k8supdate" >}}
|
||||
|
||||
You can use Kubernetes’ rolling update mechanism to upgrade the Istio CNI components.
|
||||
This is suitable for cases where `kubectl apply` was used to deploy Istio CNI.
|
||||
you can check whether Istio CNI is already installed and to upgrade it. You can use Kubernetes’ rolling update mechanism to upgrade the Istio CNI components. This is suitable for cases where `kubectl apply` was used to deploy Istio CNI.
|
||||
|
||||
1. To check whether `istio-cni` is installed, search for `istio-cni-node` pods
|
||||
and in which namespace they are running (typically, `kube-system` or `istio-system`):
|
||||
|
|
@ -63,57 +56,8 @@ This is suitable for cases where `kubectl apply` was used to deploy Istio CNI.
|
|||
$ helm template install/kubernetes/helm/istio-cni --name=istio-cni --namespace=kube-system | kubectl apply -f -
|
||||
{{< /text >}}
|
||||
|
||||
{{< /tab >}}
|
||||
|
||||
{{< tab name="Helm upgrade" category-value="helmupgrade" >}}
|
||||
|
||||
If you installed Istio CNI using [Helm and Tiller](/docs/setup/install/helm/#option-2-install-with-helm-and-tiller-via-helm-install),
|
||||
the preferred upgrade option is to let Helm take care of the upgrade.
|
||||
|
||||
1. Check whether `istio-cni` is installed, and in which namespace:
|
||||
|
||||
{{< text bash >}}
|
||||
$ helm status istio-cni
|
||||
{{< /text >}}
|
||||
|
||||
1. (Re-)install or upgrade `istio-cni` depending on the status:
|
||||
|
||||
* If `istio-cni` is not currently installed and you decide to install it:
|
||||
|
||||
{{< text bash >}}
|
||||
$ helm install install/kubernetes/helm/istio-cni --name istio-cni --namespace kube-system
|
||||
{{< /text >}}
|
||||
|
||||
* If `istio-cni` is currently installed in a namespace other than `kube-system`
|
||||
(for example, `istio-system`), delete it:
|
||||
|
||||
{{< text bash >}}
|
||||
$ helm delete --purge istio-cni
|
||||
{{< /text >}}
|
||||
|
||||
Then install it again in the `kube-system` namespace:
|
||||
|
||||
{{< text bash >}}
|
||||
$ helm install install/kubernetes/helm/istio-cni --name istio-cni --namespace kube-system
|
||||
{{< /text >}}
|
||||
|
||||
* If `istio-cni` is currently installed in the `kube-system` namespace, upgrade it:
|
||||
|
||||
{{< text bash >}}
|
||||
$ helm upgrade istio-cni install/kubernetes/helm/istio-cni --namespace kube-system
|
||||
{{< /text >}}
|
||||
|
||||
{{< /tab >}}
|
||||
{{< /tabset >}}
|
||||
|
||||
### Control plane upgrade
|
||||
|
||||
Pilot, Galley, Policy, Telemetry and Sidecar injector.
|
||||
Choose one of the following **mutually exclusive** options
|
||||
to update the control plane:
|
||||
|
||||
{{< tabset category-name="controlplaneupdate" >}}
|
||||
{{< tab name="Kubernetes rolling update" category-value="k8supdate" >}}
|
||||
You can use Kubernetes’ rolling update mechanism to upgrade the control plane components.
|
||||
This is suitable for cases where `kubectl apply` was used to deploy the Istio components,
|
||||
including configurations generated using
|
||||
|
|
@ -142,30 +86,6 @@ After this process finishes, your Istio control plane should be updated to the n
|
|||
Your existing application should continue to work without any change. If there is any
|
||||
critical issue with the new control plane, you can rollback the changes by applying the
|
||||
yaml files from the old version.
|
||||
{{< /tab >}}
|
||||
|
||||
{{< tab name="Helm upgrade" category-value="helmupgrade" >}}
|
||||
If you installed Istio using [Helm and Tiller](/docs/setup/install/helm/#option-2-install-with-helm-and-tiller-via-helm-install),
|
||||
the preferred upgrade option is to let Helm take care of the upgrade.
|
||||
|
||||
1. Upgrade the `istio-init` chart to update all the Istio [Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/#customresourcedefinitions) (CRDs).
|
||||
|
||||
{{< text bash >}}
|
||||
$ helm upgrade --install istio-init install/kubernetes/helm/istio-init --namespace istio-system
|
||||
{{< /text >}}
|
||||
|
||||
1. {{< boilerplate verify-crds >}}
|
||||
|
||||
1. Upgrade the `istio` chart:
|
||||
|
||||
{{< text bash >}}
|
||||
$ helm upgrade istio install/kubernetes/helm/istio --namespace istio-system
|
||||
{{< /text >}}
|
||||
|
||||
If Istio CNI is installed, enable it by adding the `--set istio_cni.enabled=true` setting.
|
||||
|
||||
{{< /tab >}}
|
||||
{{< /tabset >}}
|
||||
|
||||
### Sidecar upgrade
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue