Merge pull request #1831 from Felixnoo/update-canary
Update Docs: Canary Release
Patrick-LuoYu
GitHub
|
|
@ -29,7 +29,7 @@ This method serves as an efficient way to test performance and reliability of a
|
|||
|
||||
4. On the **Grayscale Release Version** tab, add another version of it (e.g `kubesphere/examples-bookinfo-reviews-v2:1.13.0`; change `v1` to `v2`) as shown in the image below and click **Next**:
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -39,27 +39,27 @@ This method serves as an efficient way to test performance and reliability of a
|
|||
|
||||
5. You send traffic to these two versions (`v1` and `v2`) either by a specific percentage or by the request content such as `Http Header`, `Cookie` and `URI`. Select **Forward by traffic ratio** and drag the icon in the middle to change the percentage of traffic sent to these two versions respectively (for example, set 50% for either one). When you finish, click **Create**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Step 2: Verify the Canary Release
|
||||
|
||||
Now that you have two available app versions, access the app to verify the canary release.
|
||||
|
||||
1. Visit the Bookinfo website and refresh your browser repeatedly. You will be able to see the **Book Reviews** section switching between v1 and v2 at a rate of 50%.
|
||||
1. Visit the Bookinfo website and refresh your browser repeatedly. You can see that the **Book Reviews** section switching between v1 and v2 at a rate of 50%.
|
||||
|
||||
|
||||
|
||||
2. The canary release job created displays under the tab **Job Status**. Click it to view details.
|
||||
2. The created canary release job is displayed under the tab **Job Status**. Click it to view details.
|
||||
|
||||
|
||||
|
||||
|
||||
3. You can see half of the traffic goes to each of them:
|
||||
|
||||
|
||||
|
||||
|
||||
4. The new Deployment is created as well.
|
||||
|
||||
|
||||
|
||||
|
||||
5. You can directly get the virtual Service to identify the weight by executing the following command:
|
||||
|
||||
|
|
@ -69,7 +69,7 @@ Now that you have two available app versions, access the app to verify the canar
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
- When you execute the command above, replace `demo-project` with your own project (i.e. namespace) name.
|
||||
- When you execute the command above, replace `demo-project` with your own project (namely, namespace) name.
|
||||
- If you want to execute the command from the web kubectl on the KubeSphere console, you need to use the account `admin`.
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -136,7 +136,7 @@ If everything runs smoothly, you can bring all the traffic to the new version.
|
|||
|
||||
1. In **Grayscale Release**, click the canary release job.
|
||||
|
||||
2. In the dialog that appears, click the three dots of **reviews v2** and select **Take Over**. It means 100% of the traffic will be sent to the new version (v2).
|
||||
2. In the displayed dialog box, click <img src="/images/docs/project-user-guide/grayscale-release/canary-release/three-dots.png" width="20px" /> on the right of **reviews v2** and select **Take Over**. It means 100% of the traffic will be sent to the new version (v2).
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -55,11 +55,11 @@ KubeSphere 基于 [Istio](https://istio.io/) 向用户提供部署金丝雀服
|
|||
|
||||
3. 您可以看到每个版本分别收到一半流量：
|
||||
|
||||
|
||||
|
||||
|
||||
4. 新的部署也已创建。
|
||||
|
||||
|
||||
|
||||
|
||||
5. 您可以执行以下命令直接获取虚拟服务来识别权重：
|
||||
|
||||
|
|
@ -136,7 +136,7 @@ KubeSphere 提供基于 [Jaeger](https://www.jaegertracing.io/) 的分布式追
|
|||
|
||||
1. 在**灰度发布**中，点击金丝雀发布任务。
|
||||
|
||||
2. 在出现的对话框中，点击 **reviews v2** 的三个点，选择**接管所有流量**。这代表 100% 的流量将会被发送到新版本 (v2)。
|
||||
2. 在弹出的对话框中，点击 **reviews v2** 右侧的 <img src="/images/docs/zh-cn/project-user-guide/grayscale-release/canary-release/three-dots.png" width="20px" />，选择**接管所有流量**。这代表 100% 的流量将会被发送到新版本 (v2)。
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 84 KiB |
|
After Width: | Height: | Size: 304 KiB |
|
Before Width: | Height: | Size: 842 KiB |
|
After Width: | Height: | Size: 283 KiB |
|
Before Width: | Height: | Size: 92 KiB |
|
After Width: | Height: | Size: 542 KiB |
|
Before Width: | Height: | Size: 89 KiB |
|
After Width: | Height: | Size: 657 KiB |
|
Before Width: | Height: | Size: 93 KiB |
|
After Width: | Height: | Size: 753 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
Before Width: | Height: | Size: 153 KiB After Width: | Height: | Size: 431 KiB |
|
Before Width: | Height: | Size: 113 KiB After Width: | Height: | Size: 690 KiB |
|
Before Width: | Height: | Size: 147 KiB After Width: | Height: | Size: 987 KiB |
|
Before Width: | Height: | Size: 126 KiB After Width: | Height: | Size: 366 KiB |
|
Before Width: | Height: | Size: 58 KiB |
|
After Width: | Height: | Size: 569 KiB |
|
Before Width: | Height: | Size: 93 KiB |
|
After Width: | Height: | Size: 767 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
Before Width: | Height: | Size: 243 KiB After Width: | Height: | Size: 425 KiB |
|
Before Width: | Height: | Size: 138 KiB After Width: | Height: | Size: 680 KiB |
|
Before Width: | Height: | Size: 232 KiB After Width: | Height: | Size: 1016 KiB |
|
Before Width: | Height: | Size: 215 KiB After Width: | Height: | Size: 360 KiB |