From eadd0947ecbba02fc5afb2842c5640c9eca7f3c3 Mon Sep 17 00:00:00 2001 From: Morven Cao Date: Thu, 27 Aug 2020 20:59:10 +0800 Subject: [PATCH] fix incorrect label for upgrade. (#8038) --- content/en/docs/setup/upgrade/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/setup/upgrade/index.md b/content/en/docs/setup/upgrade/index.md index 1bb793b025..8fb130514c 100644 --- a/content/en/docs/setup/upgrade/index.md +++ b/content/en/docs/setup/upgrade/index.md @@ -74,7 +74,7 @@ based on the namespace label `istio.io/rev`. To upgrade the namespace `test-ns`, remove the `istio-injection` label, and add the `istio.io/rev` label to point to the `canary` revision. The `istio-injection` label must be removed because it takes precedence over the `istio.io/rev` label for backward compatibility. {{< text bash >}} -$ kubectl label namespace test-ns istio-injection- istio.io/rev=istio-canary +$ kubectl label namespace test-ns istio-injection- istio.io/rev=canary {{< /text >}} After the namespace updates, you need to restart the pods to trigger re-injection. One way to do @@ -89,7 +89,7 @@ When the pods are re-injected, they will be configured to point to the `istiod-c For example, the following command will show all the pods using the `canary` revision: {{< text bash >}} -$ kubectl get pods -n test-ns -l istio.io/rev=istio-canary +$ kubectl get pods -n test-ns -l istio.io/rev=canary {{< /text >}} To verify that the new pods in the `test-ns` namespace are using the `istiod-canary` service corresponding to the `canary` revision, select one newly created pod and use the `pod_name` in the following command: