After the control plane of a Service Mesh (ASM) instance is upgraded, you also need to upgrade the sidecar proxies for Istio-enabled applications on the ASM instance. This topic describes how to upgrade sidecar proxies by using automatic sidecar proxy injection and manual sidecar proxy injection.
You have connected to a Container Service for Kubernetes (ACK) cluster by using kubectl. For more information, see Obtain the kubeconfig file of a cluster and use kubectl to connect to the cluster.
Sidecar proxies are deployed on the data plane. When you upgrade sidecar proxies, you need to update the kubeconfig file of the data plane instead of the ASM instance. Therefore, you need to obtain the kubeconfig file from the ACK console instead of the ASM console.
Automatic sidecar proxy injection
If automatic sidecar proxy injection is enabled, you can redeploy your workloads. New sidecar proxies are automatically injected.
Log on to the ACK console and click Clusters in the left-side navigation pane.
On the Clusters page, click the name of a cluster and choose in the left-side navigation pane.
On the Deployments page, perform the following operations to redeploy the workloads.
In the Actions column, find the workload that you want to redeploy and choose. In the Redeploy message that appears, click Confirm.
Select multiple workloads in the Name column and click Batch Redeploy in the lower part of the page. In the Confirm message that appears, click OK.
Manual sidecar proxy injection
If automatic sidecar proxy injection is disabled, run the following command to upgrade sidecar proxies.
Create a deployment YAML file and run the kubectl apply command.
kubectl apply -f <(istioctl kube-inject -f <A raw application YAML file with no sidecar proxy configuration injected>)