kubevela
/
kubevela.github.io
mirror of https://github.com/kubevela/kubevela.github.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix demo error (#310) 

fix docs error
This commit is contained in:
wyike 2021-09-28 20:39:35 +08:00 committed by GitHub
parent 504e0436fa
commit ad813e1c40
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/case-studies/canary-blue-green.md
View File

@ -175,7 +175,7 @@ It can be seen that the new version of the page has changed from the previous bl
If the service is found to meet expectations during manual verification, the Workflow needs to be continued to complete the full release. You can do that by executing the following command.
```shell
vela workflow reumse book-info
vela workflow resume book-info
```
If you continue to verify the webpage several times on the browser, you will find that the five-pointed star will always be red.

2
i18n/zh/docusaurus-plugin-content-docs/version-v1.1/case-studies/canary-blue-green.md
View File

@ -175,7 +175,7 @@ kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/
如果在人工校验时，发现服务符合预期，需要继续执行工作流，完成全量发布。你可以通过执行下面的命令完成这一操作。
```shell
vela workflow reumse book-info
vela workflow resume book-info
```
在浏览器上继续多次访问网页，会发现五角星将一直是红色的。

8
versioned_docs/version-v1.1/case-studies/canary-blue-green.md
View File

@ -30,7 +30,7 @@ kubectl label namespace default istio-injection=enabled
Deploy the Application of `bookinfo`:
```shell
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/blob/master/docs/examples/canary-rollout-use-case/first-deploy.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/canary-rollout-use-case/first-deploy.yaml
```
The component architecture and relationship of the application are as follows:
@ -84,7 +84,7 @@ Next, we take the `reviews` Component as an example to simulate the complete pro
Execute the following command to update the application.
```shell
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/blob/master/docs/examples/canary-rollout-use-case/rollout-v2.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/canary-rollout-use-case/rollout-v2.yaml
```
This operation updates the mirror of the `reviews` Component from the previous v2 to v3. At the same time, the Rollout Trait of the `reviews` Component specifies that the number of target instances to be upgraded is two, which are upgraded in two batches, with one instance in each batch.
@ -175,7 +175,7 @@ It can be seen that the new version of the page has changed from the previous bl
If the service is found to meet expectations during manual verification, the Workflow needs to be continued to complete the full release. You can do that by executing the following command.
```shell
vela workflow reumse book-info
vela workflow resume book-info
```
If you continue to verify the webpage several times on the browser, you will find that the five-pointed star will always be red.
@ -185,7 +185,7 @@ If you continue to verify the webpage several times on the browser, you will fin
During the manual verification, if the service does not meet the expectations, you can terminate the pre-defined release workflow and rollback the instances and the traffic to the previous version.
```shell
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/blob/master/docs/examples/canary-rollout-use-case/rollback.yaml
kubectl apply -f https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/canary-rollout-use-case/rollback.yaml
```
This is basically updates the workflow to rollback step: