Merge pull request #1861 from Felixnoo/update-gb
Update Docs: Blue-Green Deployment
|
|
@ -20,15 +20,15 @@ The blue-green release provides a zero downtime deployment, which means the new
|
|||
|
||||
## Create a Blue-green Deployment Job
|
||||
|
||||
1. Log in to KubeSphere as `project-regular` and navigate to **Grayscale Release**. Under **Categories**, click **Create Job** on the right of **Blue-green Deployment**.
|
||||
1. Log in to KubeSphere as `project-regular` and go to **Grayscale Release**. Under **Categories**, click **Create Job** on the right of **Blue-green Deployment**.
|
||||
|
||||
2. Set a name for it and click **Next**.
|
||||
|
||||
3. On the **Grayscale Release Components** tab, select your app from the drop-down list and the Service for which you want to implement the blue-green deployment. If you also use the sample app Bookinfo, select **reviews** and click **Next**.
|
||||
|
||||
4. On the **Grayscale Release Version** tab, add another version (e.g `v2`) as shown in the image below and click **Next**:
|
||||
4. On the **Grayscale Release Version** tab, add another version (e.g `v2`) as shown in the following figure and click **Next**:
|
||||
|
||||

|
||||

|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -38,19 +38,19 @@ The blue-green release provides a zero downtime deployment, which means the new
|
|||
|
||||
5. On the **Policy Config** tab, to allow the app version `v2` to take over all the traffic, select **Take over all traffic** and click **Create**.
|
||||
|
||||
6. The blue-green deployment job created displays under the tab **Job Status**. Click it to view details.
|
||||
6. The blue-green deployment job created is displayed under the tab **Job Status**. Click it to view details.
|
||||
|
||||

|
||||

|
||||
|
||||
7. Wait for a while and you can see all the traffic go to the version `v2`:
|
||||
|
||||

|
||||

|
||||
|
||||
8. The new **Deployment** is created as well.
|
||||
|
||||

|
||||

|
||||
|
||||
9. You can directly get the virtual service to identify the weight by executing the following command:
|
||||
9. You can get the virtual service to identify the weight by running the following command:
|
||||
|
||||
```bash
|
||||
kubectl -n demo-project get virtualservice -o yaml
|
||||
|
|
@ -58,8 +58,8 @@ The blue-green release provides a zero downtime deployment, which means the new
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
- When you execute the command above, replace `demo-project` with your own project (i.e. namespace) name.
|
||||
- If you want to execute the command from the web kubectl on the KubeSphere console, you need to use the account `admin`.
|
||||
- When you run the command above, replace `demo-project` with your own project (namely, namespace) name.
|
||||
- If you want to run the command from the web kubectl on the KubeSphere console, you need to use the account `admin`.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -85,5 +85,5 @@ The blue-green release provides a zero downtime deployment, which means the new
|
|||
|
||||
After you implement the blue-green deployment, and the result meets your expectation, you can take the task offline with the version `v1` removed by clicking **Job offline**.
|
||||
|
||||

|
||||

|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ weight: 10520
|
|||
|
||||
## 创建蓝绿部署任务
|
||||
|
||||
1. 以 `project-regular` 身份登录 KubeSphere,转到**灰度发布**页面,在**灰度策略**选项卡下,点击**蓝绿部署**右侧的**发布任务**。
|
||||
1. 以 `project-regular` 身份登录 KubeSphere,前往**灰度发布**页面,在**灰度策略**选项卡下,点击**蓝绿部署**右侧的**发布任务**。
|
||||
|
||||
2. 输入名称然后点击**下一步**。
|
||||
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 83 KiB |
|
After Width: | Height: | Size: 397 KiB |
|
Before Width: | Height: | Size: 93 KiB |
|
After Width: | Height: | Size: 575 KiB |
|
Before Width: | Height: | Size: 92 KiB |
|
After Width: | Height: | Size: 556 KiB |
|
Before Width: | Height: | Size: 92 KiB |
|
After Width: | Height: | Size: 270 KiB |
|
Before Width: | Height: | Size: 91 KiB |
|
After Width: | Height: | Size: 759 KiB |