After upgrading the control plane, you must also upgrade the sidecar proxies for your Istio-enabled applications. This topic describes two methods: automatic and manual sidecar proxy injection.
Prerequisites
Connect to your ACK cluster by using kubectl. For details, see Obtain the kubeconfig file of a cluster and use kubectl to connect to the cluster.
Background
Sidecar upgrades are performed in the Kubernetes cluster of the data plane. The kubeconfig must be for this cluster, not for the ASM instance. Therefore, obtain the kubeconfig from the Container Service console, not from the Service Mesh console.
Automatic sidecar proxy injection
If you use automatic sidecar proxy injection, redeploying the workload automatically injects the new sidecar proxy.
Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click .
-
On the Deployments page, redeploy the workloads by using one of the following methods:
Scenario
Actions
Single workload
In the Actions column, choose for the target workload. In the Redeploy dialog box, click OK.
Multiple workloads
In the Name column, select the target workloads. At the bottom of the page, click Batch Redeploy. In the OK dialog box, click OK.
Manual sidecar proxy injection
If your workload does not use automatic sidecar proxy injection, run the following command to manually upgrade the sidecar proxy.
Regenerate the deployment YAML file using the same manual injection method, and then reapply it with the kubectl apply command.
kubectl apply -f <(istioctl kube-inject -f <A raw application YAML file without an injected sidecar proxy>)